Handling collisions between multiple acknowledgement transmissions and an uplink data transmission

ABSTRACT

Methods, systems, and devices for wireless communications are described. A base station may transmit a downlink control transmission and multiple downlink data transmissions to a user equipment (UE). The UE may schedule an uplink data transmission based on the downlink control transmission and may schedule transmission acknowledgement messages based on the multiple downlink data transmissions. The UE may identify that the scheduled uplink data transmission overlaps with the scheduled transmission acknowledgement messages. The UE may generate one or more acknowledgement codebooks for transmission of the multiple transmission acknowledgment messages and may multiplex the one or more acknowledgement codebooks with the uplink data transmission on the uplink data channel. In some cases, the UE may multiplex the codebooks based on determining that a set of timing thresholds are satisfied by an earliest of the multiple transmission acknowledgement messages and the uplink data transmission with respect to one or more downlink transmissions.

CROSS REFERENCE

The present Application for Patent claims the benefit of U.S.Provisional Patent Application No. 62/830,146 by YANG et al., entitled“HANDLING COLLISIONS BETWEEN MULTIPLE ACKNOWLEDGEMENT TRANSMISSIONS ANDAN UPLINK DATA TRANSMISSION,” filed Apr. 5, 2019, assigned to theassignee hereof, and expressly incorporated by reference herein.

BACKGROUND

The following relates generally to wireless communications, and morespecifically to handling collisions between multiple acknowledgementtransmissions and an uplink data transmission.

Wireless communications systems are widely deployed to provide varioustypes of communication content such as voice, video, packet data,messaging, broadcast, and so on. These systems may be capable ofsupporting communication with multiple users by sharing the availablesystem resources (e.g., time, frequency, and power). Examples of suchmultiple-access systems include fourth generation (4G) systems such asLong Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, orLTE-A Pro systems, and fifth generation (5G) systems which may bereferred to as New Radio (NR) systems. These systems may employtechnologies such as code division multiple access (CDMA), time divisionmultiple access (TDMA), frequency division multiple access (FDMA),orthogonal frequency division multiple access (OFDMA), or discreteFourier transform spread orthogonal frequency division multiplexing(DFT-S-OFDM). A wireless multiple-access communications system mayinclude a number of base stations or network access nodes, eachsimultaneously supporting communication for multiple communicationdevices, which may be otherwise known as user equipment (UE).

In some cases, a base station may transmit one or more physical downlinkcontrol channel (PDCCH) transmissions to a UE which may scheduleresources for receiving downlink transmissions or transmitting uplinktransmissions. If the UE receives a PDCCH scheduling one or moredownlink transmissions, the UE may transmit feedback to the base stationindicating whether the UE correctly decoded the one or more downlinktransmissions. The UE may indicate the feedback in the form of acodebook (e.g., an acknowledgement codebook.

SUMMARY

The described techniques relate to improved methods, systems, devices,and apparatuses that support handling collisions between multipleacknowledgement transmissions and an uplink data transmission.Generally, the described techniques provide for a base station totransmit one or more downlink control transmissions and multipledownlink data transmissions to a user equipment (UE). Some downlinkcontrol transmissions may provide the UE with details regarding thedownlink data transmissions to be received by the UE. Another downlinkcontrol transmission may provide the UE with details regarding an uplinkdata transmission to be scheduled by the UE. The UE may determineresources for an uplink data transmission based on one of the downlinkcontrol transmissions and may determine resources for transmissionacknowledgement messages based on the multiple downlink datatransmissions. The UE may identify that the scheduled uplink datatransmission overlaps with the scheduled transmission acknowledgementmessages. The UE may generate one or more acknowledgement codebooks(e.g., hybrid automatic repeat request (HARQ) acknowledgement (ACK)codebooks) for transmission of the multiple transmission acknowledgmentmessages and may multiplex the one or more acknowledgement codebookswith the uplink data transmission on the uplink data channel.

In some cases, the UE may multiplex the one or more acknowledgementcodebooks based on determining that a set of timing thresholds aresatisfied by an earliest of the multiple transmission acknowledgementmessages and the uplink data transmission with respect to a latestdownlink data transmission acknowledged by one of the multipletransmission acknowledgement messages and a downlink control channeltransmission that schedules uplink transmissions for the slot.Additionally or alternatively, the UE may multiplex the one or moreacknowledgement codebooks based on determining whether downlink controlinformation scheduling one or more downlink data transmissions isreceived after the downlink control transmission that schedules theuplink transmissions for the slot.

In some cases, generating the one or more acknowledgement codebooks mayinvolve separately encoding each of the multiple transmissionacknowledgement messages to corresponding coded acknowledgementcodebooks, where the corresponding acknowledgement codebooks may bemapped to the uplink data channel. Alternatively, generating the one ormore acknowledgement codebooks may involve jointly encoding the multipletransmission acknowledgement messages to a single coded acknowledgementcodebook, where the single coded acknowledgement codebook is mapped tothe uplink data channel. In either case, the UE may determine a numberof bits to insert into a set of separate acknowledgement codebooks orinto a concatenation of the set of separate acknowledgement codebooks toform the corresponding acknowledgement codebooks or the single codedacknowledgement codebook. The UE may determine the number of bits basedon an uplink downlink assignment indication (DAI) and one or moredownlink DAIs.

A method of wireless communication at a UE is described. The method mayinclude identifying that an uplink data transmission scheduled in a slotoverlaps with multiple scheduled transmission acknowledgement messages,determining that a set of timing thresholds are satisfied by an earliestof the multiple scheduled transmission acknowledgement messages and theuplink data transmission with respect to a latest downlink datatransmission acknowledged by one of the multiple scheduled transmissionacknowledgement messages and a downlink control transmission thatschedules the uplink data transmission, generating one or moreacknowledgement codebooks for transmission of the multiple scheduledtransmission acknowledgement messages, and multiplexing, based on theset of timing thresholds being satisfied, the one or moreacknowledgement codebooks with the uplink data transmission on an uplinkdata channel.

An apparatus for wireless communication at a UE is described. Theapparatus may include a processor, memory coupled with the processor,and instructions stored in the memory. The instructions may beexecutable by the processor to cause the apparatus to identify that anuplink data transmission scheduled in a slot overlaps with multiplescheduled transmission acknowledgement messages, determine that a set oftiming thresholds are satisfied by an earliest of the multiple scheduledtransmission acknowledgement messages and the uplink data transmissionwith respect to a latest downlink data transmission acknowledged by oneof the multiple scheduled transmission acknowledgement messages and adownlink control transmission that schedules the uplink datatransmission, generate one or more acknowledgement codebooks fortransmission of the multiple scheduled transmission acknowledgementmessages, and multiplex, based on the set of timing thresholds beingsatisfied, the one or more acknowledgement codebooks with the uplinkdata transmission on an uplink data channel.

Another apparatus for wireless communication at a UE is described. Theapparatus may include means for identifying that an uplink datatransmission scheduled in a slot overlaps with multiple scheduledtransmission acknowledgement messages, determining that a set of timingthresholds are satisfied by an earliest of the multiple scheduledtransmission acknowledgement messages and the uplink data transmissionwith respect to a latest downlink data transmission acknowledged by oneof the multiple scheduled transmission acknowledgement messages and adownlink control transmission that schedules the uplink datatransmission, generating one or more acknowledgement codebooks fortransmission of the multiple scheduled transmission acknowledgementmessages, and multiplexing, based on the set of timing thresholds beingsatisfied, the one or more acknowledgement codebooks with the uplinkdata transmission on an uplink data channel.

A non-transitory computer-readable medium storing code for wirelesscommunication at a UE is described. The code may include instructionsexecutable by a processor to identify that an uplink data transmissionscheduled in a slot overlaps with multiple scheduled transmissionacknowledgement messages, determine that a set of timing thresholds aresatisfied by an earliest of the multiple scheduled transmissionacknowledgement messages and the uplink data transmission with respectto a latest downlink data transmission acknowledged by one of themultiple scheduled transmission acknowledgement messages and a downlinkcontrol transmission that schedules the uplink data transmission,generate one or more acknowledgement codebooks for transmission of themultiple scheduled transmission acknowledgement messages, and multiplex,based on the set of timing thresholds being satisfied, the one or moreacknowledgement codebooks with the uplink data transmission on an uplinkdata channel.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, determining that the set oftiming thresholds may be satisfied may include operations, features,means, or instructions for determining that a first timing threshold maybe satisfied by the earliest of the multiple scheduled transmissionacknowledgement messages and the uplink data transmission being at leasta first predetermined number of symbols after a last symbol of thelatest downlink data transmission acknowledged by one of the multipletransmission acknowledgment messages, and determining that a secondtiming threshold may be satisfied by the earliest of the multiplescheduled transmission acknowledgement messages and the uplink datatransmission being at least a second predetermined number of symbolsafter a last symbol of the downlink control transmission that schedulesthe uplink data transmission.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for determining thatdownlink control information scheduling downlink data transmissions maybe received before the downlink control transmission that schedules theuplink data transmission, where multiplexing the one or moreacknowledgement codebooks with the uplink data transmission may befurther based on the downlink control information being received beforethe downlink control transmission.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for determining thatdownlink control information scheduling one or more downlink datatransmissions may be received after the downlink control transmissionthat schedules the uplink data transmission, where acknowledgementcodebooks corresponding to responsive transmission acknowledgementmessages associated with the one or more downlink data transmissionsreceived after the downlink control transmission may be not included ingenerating the one or more acknowledgement codebooks.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, generating the one or moreacknowledgement codebooks for transmission of the multiple scheduledtransmission acknowledgement messages may include operations, features,means, or instructions for separately encoding each of the multiplescheduled transmission acknowledgement messages to corresponding codedacknowledgment codebooks, where the corresponding acknowledgementcodebooks may be each mapped to the uplink data channel.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, generating the one or moreacknowledgement codebooks for transmission of the multiple scheduledtransmission acknowledgement messages may include operations, features,means, or instructions for jointly encoding the multiple scheduledtransmission acknowledgement messages to a single coded acknowledgementcodebook, where the single coded acknowledgement codebook may be mappedto the uplink data channel.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for receiving a set offirst indications of acknowledgement payload size, each of the set offirst indications corresponding to one of the multiple scheduledtransmission acknowledgement messages and being received via respectivedownlink control information messages scheduling downlink datatransmissions acknowledged by the multiple scheduled transmissionacknowledgement messages, and receiving a single second indication ofacknowledgement payload size via the downlink control transmission thatschedules the uplink data transmission.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, generating the one or moreacknowledgement codebooks for transmission of the multiple scheduledtransmission acknowledgement messages may include operations, features,means, or instructions for generating a separate acknowledgementcodebook for each of the multiple scheduled transmission acknowledgementmessages based on respective ones of the set of first indications, andpadding at least one or more of the separate acknowledgement codebooksaccording to the single second indication to generate a set of updatedacknowledgement codebooks for multiplexing the one or moreacknowledgement codebooks with the uplink data transmission.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for concatenating each ofthe set of updated acknowledgement codebooks prior to multiplexing theone or more acknowledgement codebooks with the uplink data transmission.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, generating the one or moreacknowledgement codebooks for transmission of the multiple scheduledtransmission acknowledgement messages may include operations, features,means, or instructions for generating a separate acknowledgementcodebook for each of the multiple scheduled transmission acknowledgementmessages based on respective ones of the set of first indications,concatenating the separate acknowledgement codebooks for each of themultiple scheduled transmission acknowledgement messages, and applyingthe single second indication to the concatenated acknowledgementcodebooks to generate a single updated acknowledgement codebook formultiplexing the one or more acknowledgement codebooks with the uplinkdata transmission.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the multiple scheduledtransmission acknowledgement messages may be each scheduled to betransmitted via separate physical uplink control channel transmissionswithin the slot.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the multiple scheduledtransmission acknowledgement messages may be scheduled to be transmittedon a first carrier that may have a higher sub-carrier spacing than thatof a second carrier used by the uplink data transmission, and where themultiple scheduled transmission acknowledgement messages may be eachscheduled to be transmitted via separate physical uplink control channeltransmissions within corresponding slots of the first carrier.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the multiple scheduledtransmission acknowledgement messages and the uplink data transmissionmay be each associated with a same traffic type.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the same traffic type may beultra-reliable low-latency communications traffic.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the same traffic type may beenhanced mobile broadband traffic.

A method of wireless communication at a base station is described. Themethod may include transmitting, to a UE, a downlink controltransmission scheduling an uplink data transmission for the UE during aslot, transmitting, to the UE, multiple downlink data transmissions thatare to be acknowledged by the UE via corresponding multiple transmissionacknowledgment messages that are scheduled to at least partially overlapin time with the uplink data transmission, and receiving, from the UE,one or more acknowledgement codebooks corresponding to the multipletransmission acknowledgement messages, where the one or moreacknowledgement codebooks are multiplexed with the uplink datatransmission based on a set of timing thresholds being satisfied by anearliest of the multiple transmission acknowledgement messages and theuplink data transmission with respect to a latest downlink datatransmission of the multiple downlink data transmissions and thedownlink control transmission scheduling the uplink data transmission.

An apparatus for wireless communication at a base station is described.The apparatus may include a processor, memory coupled with theprocessor, and instructions stored in the memory. The instructions maybe executable by the processor to cause the apparatus to transmit, to aUE, a downlink control transmission scheduling an uplink datatransmission for the UE during a slot, transmit, to the UE, multipledownlink data transmissions that are to be acknowledged by the UE viacorresponding multiple transmission acknowledgment messages that arescheduled to at least partially overlap in time with the uplink datatransmission, and receive, from the UE, one or more acknowledgementcodebooks corresponding to the multiple transmission acknowledgementmessages, where the one or more acknowledgement codebooks aremultiplexed with the uplink data transmission based on a set of timingthresholds being satisfied by an earliest of the multiple transmissionacknowledgement messages and the uplink data transmission with respectto a latest downlink data transmission of the multiple downlink datatransmissions and the downlink control transmission scheduling theuplink data transmission.

Another apparatus for wireless communication at a base station isdescribed. The apparatus may include means for transmitting, to a UE, adownlink control transmission scheduling an uplink data transmission forthe UE during a slot, transmitting, to the UE, multiple downlink datatransmissions that are to be acknowledged by the UE via correspondingmultiple transmission acknowledgment messages that are scheduled to atleast partially overlap in time with the uplink data transmission, andreceiving, from the UE, one or more acknowledgement codebookscorresponding to the multiple transmission acknowledgement messages,where the one or more acknowledgement codebooks are multiplexed with theuplink data transmission based on a set of timing thresholds beingsatisfied by an earliest of the multiple transmission acknowledgementmessages and the uplink data transmission with respect to a latestdownlink data transmission of the multiple downlink data transmissionsand the downlink control transmission scheduling the uplink datatransmission.

A non-transitory computer-readable medium storing code for wirelesscommunication at a base station is described. The code may includeinstructions executable by a processor to transmit, to a UE, a downlinkcontrol transmission scheduling an uplink data transmission for the UEduring a slot, transmit, to the UE, multiple downlink data transmissionsthat are to be acknowledged by the UE via corresponding multipletransmission acknowledgment messages that are scheduled to at leastpartially overlap in time with the uplink data transmission, andreceive, from the UE, one or more acknowledgement codebookscorresponding to the multiple transmission acknowledgement messages,where the one or more acknowledgement codebooks are multiplexed with theuplink data transmission based on a set of timing thresholds beingsatisfied by an earliest of the multiple transmission acknowledgementmessages and the uplink data transmission with respect to a latestdownlink data transmission of the multiple downlink data transmissionsand the downlink control transmission scheduling the uplink datatransmission.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the set of timing thresholdsinclude a first timing threshold and a second timing threshold, thefirst timing threshold being satisfied by the earliest of the multipletransmission acknowledgement messages and the uplink data transmissionbeing at least a first predetermined number of symbols after a lastsymbol of the latest downlink data transmission of the multiple downlinkdata transmissions, and the second timing threshold being satisfied bythe earliest of the multiple transmission acknowledgement messages andthe uplink data transmission being at least a second predeterminednumber of symbols after a last symbol of the downlink controltransmission scheduling the uplink data transmission.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for receiving one or moreacknowledgement codebooks corresponding to the multiple transmissionacknowledgement messages and multiplexed with the uplink datatransmission may be further based on downlink control informationscheduling the multiple downlink data transmissions being received atthe UE before the downlink control transmission scheduling the uplinkdata transmission.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for transmitting a downlinkcontrol information scheduling at least one of the multiple downlinkdata transmissions such that the downlink control information may bereceived at the UE after the downlink control transmission schedulingthe uplink data transmission, where ones of the multiple transmissionacknowledgement messages that may be responsive to the at least one ofthe multiple downlink data transmissions may be not included in the oneor more acknowledgement codebooks multiplexed with the uplink datatransmission received from the UE.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, receiving one or moreacknowledgement codebooks corresponding to the multiple transmissionacknowledgement messages and multiplexed with the uplink datatransmission may include operations, features, means, or instructionsfor receiving the multiple transmission acknowledgement messages asseparately encoded acknowledgement codebooks.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, receiving one or moreacknowledgement codebooks corresponding to the multiple transmissionacknowledgement messages and multiplexed with the uplink datatransmission may include operations, features, means, or instructionsfor receiving the multiple transmission acknowledgement messages as ajointly encoded acknowledgement codebook.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for transmitting a set offirst indications of acknowledgement payload size, each of the set offirst indications corresponding to one of the multiple transmissionacknowledgement messages and being transmitted via respective downlinkcontrol information messages scheduling the multiple downlink datatransmissions, and transmitting a single second indication ofacknowledgement payload size via the downlink control transmissionscheduling the uplink data transmission.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the single second indicationmay be indicative of acknowledgement payload size for each of the one ormore acknowledgement codebooks, and wherein each of the one or moreacknowledgement codebooks is a coded acknowledgement codebook.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the single second indicationmay be indicative of a single acknowledgement payload size for all ofthe one or more acknowledgement codebooks.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the multiple transmissionacknowledgement messages may be each scheduled to be transmitted viaseparate physical uplink control channel transmissions within the slot.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the multiple transmissionacknowledgement messages may be scheduled to be transmitted on a firstcarrier that may have a higher sub-carrier spacing than that of a secondcarrier used by the uplink data transmission, and where the multipletransmission acknowledgement messages may be each scheduled to betransmitted via separate physical uplink control channel transmissionswithin corresponding slots of the first carrier.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the multiple transmissionacknowledgement messages and the uplink data transmission may be eachassociated with a same traffic type.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the same traffic type may beultra-reliable low-latency communications traffic.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the same traffic type may beenhanced mobile broadband traffic.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example of a wireless communications system thatsupports handling collisions between multiple acknowledgementtransmissions and an uplink data transmission in accordance with aspectsof the present disclosure.

FIG. 2 illustrates an example of a wireless communications system thatsupports handling collisions between multiple acknowledgementtransmissions and an uplink data transmission in accordance with aspectsof the present disclosure.

FIG. 3 illustrates an example of an acknowledgement multiplexing schemethat supports handling collisions between multiple acknowledgementtransmissions and an uplink data transmission in accordance with aspectsof the present disclosure.

FIG. 4 illustrates an example of a process flow that supports handlingcollisions between multiple acknowledgement transmissions and an uplinkdata transmission in accordance with aspects of the present disclosure.

FIGS. 5 and 6 show block diagrams of devices that support handlingcollisions between multiple acknowledgement transmissions and an uplinkdata transmission in accordance with aspects of the present disclosure.

FIG. 7 shows a block diagram of a communications manager that supportshandling collisions between multiple acknowledgement transmissions andan uplink data transmission in accordance with aspects of the presentdisclosure.

FIG. 8 shows a diagram of a system including a device that supportshandling collisions between multiple acknowledgement transmissions andan uplink data transmission in accordance with aspects of the presentdisclosure.

FIGS. 9 and 10 show block diagrams of devices that support handlingcollisions between multiple acknowledgement transmissions and an uplinkdata transmission in accordance with aspects of the present disclosure.

FIG. 11 shows a block diagram of a communications manager that supportshandling collisions between multiple acknowledgement transmissions andan uplink data transmission in accordance with aspects of the presentdisclosure.

FIG. 12 shows a diagram of a system including a device that supportshandling collisions between multiple acknowledgement transmissions andan uplink data transmission in accordance with aspects of the presentdisclosure.

FIGS. 13 through 20 show flowcharts illustrating methods that supporthandling collisions between multiple acknowledgement transmissions andan uplink data transmission in accordance with aspects of the presentdisclosure.

DETAILED DESCRIPTION

A base station may transmit downlink and uplink grants (e.g., physicaldownlink control channel (PDCCH) transmissions) to a user equipment (UE)which may schedule resources for receiving downlink transmissions ortransmitting uplink transmissions, respectively. If the UE receives adownlink grant scheduling one or more downlink transmissions, the UE maytransmit one or more transmission acknowledgement messages (e.g., hybridautomatic repeat request (HARQ) acknowledgements (ACKs)) over a physicaluplink control channel (PUCCH) to the base station indicating whetherthe UE correctly decoded the one or more downlink transmissions. The UEmay indicate the HARQ-ACKs in the form of a HARQ-ACK codebook, which maybe an example of an acknowledgement codebook. In some cases, a UE mayreceive an uplink grant scheduling an uplink transmission (e.g., aphysical uplink shared channel (PUSCH)) that collides in time (e.g., hasoverlapping time resources) with a PUCCH resource for transmitting aHARQ-ACK codebook. In such cases, the UE may piggyback the HARQ-ACKcodebook associated with the PUCCH resource on the PUSCH.

In some cases, the UE may determine or identify resources for a PUSCHtransmission that collides in time with multiple PUCCH resources fortransmitting HARQ-ACKs. Such collisions may occur if multiple PUCCHresources are scheduled on a single slot or if a slot associated withthe PUCCH resources is smaller than slots associated with PUSCHresources. In either case, resolving the collisions between the PUSCHtransmission and the PUCCH resources for transmitting HARQ-ACK mayinvolve piggybacking each of the codebooks onto the PUSCH. One method ofpiggybacking the codebooks may involve separately encoding each of theHARQ-ACK codebooks and mapping or multiplexing them sequentially to thePUSCH. Another method of piggybacking the HARQ-ACK codebooks may involveconcatenating the codebooks together, jointly encoding the HARQ-ACKcodebooks, and mapping or multiplexing the encoded concatenated HARQ-ACKcodebook to the PUSCH.

In some cases, the uplink and downlink grants may include an uplinkdownlink assignment indication (DAI) or a downlink DAI, respectively.The UE may use the uplink and downlink DAI to determine a size of aHARQ-ACK codebook to be transmitted by the UE. In some cases, thedownlink DAI may be used to determine an initial size of a HARQ-ACKcodebook to be used, while the uplink DAI may be used to update the sizeof the HARQ-ACK codebook to be used (by, for example, adding dummynegative acknowledgements (NACK) bits, if any, to HARQ-ACK codebooksassociated with each PUCCH resource or in the concatenated HARQ-ACKcodebook). In one example, an uplink grant may include a single uplinkDAI to compare against the downlink DAIS associated with each PUCCHresource for transmitting HARQ-ACKs. In such examples, the uplink DAImay indicate the size of each HARQ-ACK codebook. In another example, anuplink grant may include a single uplink DAI to compare against acombined downlink DAI, where the combined downlink DAI may represent atotal codebook size after concatenating the HARQ-ACK codebooks butbefore inserting the dummy NACK bits. In such examples, the uplink DAImay indicate the total codebook size after inserting the dummy NACKbits.

In some cases, the UE may piggyback the multiple HARQ-ACK codebooks tothe PUSCH transmission if one or more timeline conditions are satisfied.For instance, the UE may perform the piggybacking if a first symbol ofan earliest PUCCH or PUSCH among all overlapping channels starts noearlier than a timing threshold after the last symbol of a physicaldownlink shared channel (PDSCH) being acknowledged by the multipleHARQ-ACKs. Additionally or alternatively, the UE may perform thepiggybacking if a first symbol of an earliest PUCCH or PUSCH among alloverlapping channels starts no earlier than a timing threshold after alast symbol of an uplink grant scheduling uplink transmissions such asHARQ-ACK (e.g., over PUCCH) or PUSCH transmissions over a slot.Additionally or alternatively, the UE may perform the piggybacking ifthe uplink downlink control information (DCI) scheduling the PUSCHtransmission arrives after all downlink DCI corresponding to theHARQ-ACK transmissions.

Aspects of the disclosure are initially described in the context of awireless communications system. Additional aspects of the disclosure maybe further described in the context of an additional wirelesscommunications system, an acknowledgement multiplexing scheme, and aprocess flow. Aspects of the disclosure are further illustrated by anddescribed with reference to apparatus diagrams, system diagrams, andflowcharts that relate to handling collisions between multipleacknowledgement transmissions and an uplink data transmission.

FIG. 1 illustrates an example of a wireless communications system 100that supports handling collisions between multiple acknowledgementtransmissions and an uplink data transmission in accordance with aspectsof the present disclosure. The wireless communications system 100includes base stations 105, UEs 115, and a core network 130. In someexamples, the wireless communications system 100 may be a Long TermEvolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pronetwork, or a New Radio (NR) network. In some cases, wirelesscommunications system 100 may support enhanced broadband communications,ultra-reliable (e.g., mission critical) communications, low latencycommunications, or communications with low-cost and low-complexitydevices.

Base stations 105 may wirelessly communicate with UEs 115 via one ormore base station antennas. Base stations 105 described herein mayinclude or may be referred to by those skilled in the art as a basetransceiver station, a radio base station, an access point, a radiotransceiver, a NodeB, an eNodeB (eNB), a next-generation NodeB orgiga-NodeB (either of which may be referred to as a gNB), a Home NodeB,a Home eNodeB, or some other suitable terminology. Wirelesscommunications system 100 may include base stations 105 of differenttypes (e.g., macro or small cell base stations). The UEs 115 describedherein may be able to communicate with various types of base stations105 and network equipment including macro eNBs, small cell eNBs, gNBs,relay base stations, and the like.

Each base station 105 may be associated with a particular geographiccoverage area 110 in which communications with various UEs 115 issupported. Each base station 105 may provide communication coverage fora respective geographic coverage area 110 via communication links 125,and communication links 125 between a base station 105 and a UE 115 mayutilize one or more carriers. Communication links 125 shown in wirelesscommunications system 100 may include uplink transmissions from a UE 115to a base station 105, or downlink transmissions from a base station 105to a UE 115. Downlink transmissions may also be called forward linktransmissions while uplink transmissions may also be called reverse linktransmissions.

The geographic coverage area 110 for a base station 105 may be dividedinto sectors making up a portion of the geographic coverage area 110,and each sector may be associated with a cell. For example, each basestation 105 may provide communication coverage for a macro cell, a smallcell, a hot spot, or other types of cells, or various combinationsthereof. In some examples, a base station 105 may be movable andtherefore provide communication coverage for a moving geographiccoverage area 110. In some examples, different geographic coverage areas110 associated with different technologies may overlap, and overlappinggeographic coverage areas 110 associated with different technologies maybe supported by the same base station 105 or by different base stations105. The wireless communications system 100 may include, for example, aheterogeneous LTE/LTE-A/LTE-A Pro or NR network in which different typesof base stations 105 provide coverage for various geographic coverageareas 110.

The term “cell” refers to a logical communication entity used forcommunication with a base station 105 (e.g., over a carrier), and may beassociated with an identifier for distinguishing neighboring cells(e.g., a physical cell identifier (PCID), a virtual cell identifier(VCID)) operating via the same or a different carrier. In some examples,a carrier may support multiple cells, and different cells may beconfigured according to different protocol types (e.g., machine-typecommunication (MTC), narrowband Internet-of-Things (NB-IoT), enhancedmobile broadband (eMBB), or others) that may provide access fordifferent types of devices. In some cases, the term “cell” may refer toa portion of a geographic coverage area 110 (e.g., a sector) over whichthe logical entity operates.

UEs 115 may be dispersed throughout the wireless communications system100, and each UE 115 may be stationary or mobile. A UE 115 may also bereferred to as a mobile device, a wireless device, a remote device, ahandheld device, or a subscriber device, or some other suitableterminology, where the “device” may also be referred to as a unit, astation, a terminal, or a client. A UE 115 may also be a personalelectronic device such as a cellular phone, a personal digital assistant(PDA), a tablet computer, a laptop computer, or a personal computer. Insome examples, a UE 115 may also refer to a wireless local loop (WLL)station, an Internet of Things (IoT) device, an Internet of Everything(IoE) device, or an MTC device, or the like, which may be implemented invarious articles such as appliances, vehicles, meters, or the like.

Some UEs 115, such as MTC or IoT devices, may be low cost or lowcomplexity devices, and may provide for automated communication betweenmachines (e.g., via Machine-to-Machine (M2M) communication). M2Mcommunication or MTC may refer to data communication technologies thatallow devices to communicate with one another or a base station 105without human intervention. In some examples, M2M communication or MTCmay include communications from devices that integrate sensors or metersto measure or capture information and relay that information to acentral server or application program that can make use of theinformation or present the information to humans interacting with theprogram or application. Some UEs 115 may be designed to collectinformation or enable automated behavior of machines. Examples ofapplications for MTC devices include smart metering, inventorymonitoring, water level monitoring, equipment monitoring, healthcaremonitoring, wildlife monitoring, weather and geological eventmonitoring, fleet management and tracking, remote security sensing,physical access control, and transaction-based business charging.

Some UEs 115 may be configured to employ operating modes that reducepower consumption, such as half-duplex communications (e.g., a mode thatsupports one-way communication via transmission or reception, but nottransmission and reception simultaneously). In some examples half-duplexcommunications may be performed at a reduced peak rate. Other powerconservation techniques for UEs 115 include entering a power saving“deep sleep” mode when not engaging in active communications, oroperating over a limited bandwidth (e.g., according to narrowbandcommunications). In some cases, UEs 115 may be designed to supportcritical functions (e.g., mission critical functions), and a wirelesscommunications system 100 may be configured to provide ultra-reliablecommunications for these functions.

In some cases, a UE 115 may also be able to communicate directly withother UEs 115 (e.g., using a peer-to-peer (P2P) or device-to-device(D2D) protocol). One or more of a group of UEs 115 utilizing D2Dcommunications may be within the geographic coverage area 110 of a basestation 105. Other UEs 115 in such a group may be outside the geographiccoverage area 110 of a base station 105, or be otherwise unable toreceive transmissions from a base station 105. In some cases, groups ofUEs 115 communicating via D2D communications may utilize a one-to-many(1:M) system in which each UE 115 transmits to every other UE 115 in thegroup. In some cases, a base station 105 facilitates the scheduling ofresources for D2D communications. In other cases, D2D communications arecarried out between UEs 115 without the involvement of a base station105.

Base stations 105 may communicate with the core network 130 and with oneanother. For example, base stations 105 may interface with the corenetwork 130 through backhaul links 132 (e.g., via an S1, N2, N3, orother interface). Base stations 105 may communicate with one anotherover backhaul links 134 (e.g., via an X2, Xn, or other interface) eitherdirectly (e.g., directly between base stations 105) or indirectly (e.g.,via core network 130).

The core network 130 may provide user authentication, accessauthorization, tracking, Internet Protocol (IP) connectivity, and otheraccess, routing, or mobility functions. The core network 130 may be anevolved packet core (EPC), which may include at least one mobilitymanagement entity (MME), at least one serving gateway (S-GW), and atleast one Packet Data Network (PDN) gateway (P-GW). The MME may managenon-access stratum (e.g., control plane) functions such as mobility,authentication, and bearer management for UEs 115 served by basestations 105 associated with the EPC. User IP packets may be transferredthrough the S-GW, which itself may be connected to the P-GW. The P-GWmay provide IP address allocation as well as other functions. The P-GWmay be connected to the network operators IP services. The operators IPservices may include access to the Internet, Intranet(s), an IPMultimedia Subsystem (IMS), or a Packet-Switched (PS) Streaming Service.

At least some of the network devices, such as a base station 105, mayinclude subcomponents such as an access network entity, which may be anexample of an access node controller (ANC). Each access network entitymay communicate with UEs 115 through a number of other access networktransmission entities, which may be referred to as a radio head, a smartradio head, or a transmission/reception point (TRP). In someconfigurations, various functions of each access network entity or basestation 105 may be distributed across various network devices (e.g.,radio heads and access network controllers) or consolidated into asingle network device (e.g., a base station 105).

Wireless communications system 100 may operate using one or morefrequency bands, typically in the range of 300 megahertz (MHz) to 300gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is known asthe ultra-high frequency (UHF) region or decimeter band, since thewavelengths range from approximately one decimeter to one meter inlength. UHF waves may be blocked or redirected by buildings andenvironmental features. However, the waves may penetrate structuressufficiently for a macro cell to provide service to UEs 115 locatedindoors. Transmission of UHF waves may be associated with smallerantennas and shorter range (e.g., less than 100 km) compared totransmission using the smaller frequencies and longer waves of the highfrequency (HF) or very high frequency (VHF) portion of the spectrumbelow 300 MHz.

Wireless communications system 100 may also operate in a super highfrequency (SHF) region using frequency bands from 3 GHz to 30 GHz, alsoknown as the centimeter band. The SHF region includes bands such as the5 GHz industrial, scientific, and medical (ISM) bands, which may be usedopportunistically by devices that may be capable of toleratinginterference from other users.

Wireless communications system 100 may also operate in an extremely highfrequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz),also known as the millimeter band. In some examples, wirelesscommunications system 100 may support millimeter wave (mmW)communications between UEs 115 and base stations 105, and EHF antennasof the respective devices may be even smaller and more closely spacedthan UHF antennas. In some cases, this may facilitate use of antennaarrays within a UE 115. However, the propagation of EHF transmissionsmay be subject to even greater atmospheric attenuation and shorter rangethan SHF or UHF transmissions. Techniques disclosed herein may beemployed across transmissions that use one or more different frequencyregions, and designated use of bands across these frequency regions maydiffer by country or regulating body.

In some cases, wireless communications system 100 may utilize bothlicensed and unlicensed radio frequency spectrum bands. For example,wireless communications system 100 may employ License Assisted Access(LAA), LTE-Unlicensed (LTE-U) radio access technology, or NR technologyin an unlicensed band such as the 5 GHz ISM band. When operating inunlicensed radio frequency spectrum bands, wireless devices such as basestations 105 and UEs 115 may employ listen-before-talk (LBT) proceduresto ensure a frequency channel is clear before transmitting data. In somecases, operations in unlicensed bands may be based on a carrieraggregation configuration in conjunction with component carriersoperating in a licensed band (e.g., LAA). Operations in unlicensedspectrum may include downlink transmissions, uplink transmissions,peer-to-peer transmissions, or a combination of these. Duplexing inunlicensed spectrum may be based on frequency division duplexing (FDD),time division duplexing (TDD), or a combination of both.

In some examples, base station 105 or UE 115 may be equipped withmultiple antennas, which may be used to employ techniques such astransmit diversity, receive diversity, multiple-input multiple-output(MIMO) communications, or beamforming. For example, wirelesscommunications system 100 may use a transmission scheme between atransmitting device (e.g., a base station 105) and a receiving device(e.g., a UE 115), where the transmitting device is equipped withmultiple antennas and the receiving device is equipped with one or moreantennas. MIMO communications may employ multipath signal propagation toincrease the spectral efficiency by transmitting or receiving multiplesignals via different spatial layers, which may be referred to asspatial multiplexing. The multiple signals may, for example, betransmitted by the transmitting device via different antennas ordifferent combinations of antennas. Likewise, the multiple signals maybe received by the receiving device via different antennas or differentcombinations of antennas. Each of the multiple signals may be referredto as a separate spatial stream, and may carry bits associated with thesame data stream (e.g., the same codeword) or different data streams.Different spatial layers may be associated with different antenna portsused for channel measurement and reporting. MIMO techniques includesingle-user MIMO (SU-MIMO) where multiple spatial layers are transmittedto the same receiving device, and multiple-user MIMO (MU-MIMO) wheremultiple spatial layers are transmitted to multiple devices.

Beamforming, which may also be referred to as spatial filtering,directional transmission, or directional reception, is a signalprocessing technique that may be used at a transmitting device or areceiving device (e.g., a base station 105 or a UE 115) to shape orsteer an antenna beam (e.g., a transmit beam or receive beam) along aspatial path between the transmitting device and the receiving device.Beamforming may be achieved by combining the signals communicated viaantenna elements of an antenna array such that signals propagating atparticular orientations with respect to an antenna array experienceconstructive interference while others experience destructiveinterference. The adjustment of signals communicated via the antennaelements may include a transmitting device or a receiving deviceapplying certain amplitude and phase offsets to signals carried via eachof the antenna elements associated with the device. The adjustmentsassociated with each of the antenna elements may be defined by abeamforming weight set associated with a particular orientation (e.g.,with respect to the antenna array of the transmitting device orreceiving device, or with respect to some other orientation).

In one example, a base station 105 may use multiple antennas or antennaarrays to conduct beamforming operations for directional communicationswith a UE 115. For instance, some signals (e.g. synchronization signals,reference signals, beam selection signals, or other control signals) maybe transmitted by a base station 105 multiple times in differentdirections, which may include a signal being transmitted according todifferent beamforming weight sets associated with different directionsof transmission. Transmissions in different beam directions may be usedto identify (e.g., by the base station 105 or a receiving device, suchas a UE 115) a beam direction for subsequent transmission and/orreception by the base station 105.

Some signals, such as data signals associated with a particularreceiving device, may be transmitted by a base station 105 in a singlebeam direction (e.g., a direction associated with the receiving device,such as a UE 115). In some examples, the beam direction associated withtransmissions along a single beam direction may be determined based atleast in in part on a signal that was transmitted in different beamdirections. For example, a UE 115 may receive one or more of the signalstransmitted by the base station 105 in different directions, and the UE115 may report to the base station 105 an indication of the signal theUE 115 received with a highest signal quality, or an otherwiseacceptable signal quality. Although these techniques are described withreference to signals transmitted in one or more directions by a basestation 105, a UE 115 may employ similar techniques for transmittingsignals multiple times in different directions (e.g., for identifying abeam direction for subsequent transmission or reception by the UE 115),or transmitting a signal in a single direction (e.g., for transmittingdata to a receiving device).

A receiving device (e.g., a UE 115, which may be an example of a mmWreceiving device) may try multiple receive beams when receiving varioussignals from the base station 105, such as synchronization signals,reference signals, beam selection signals, or other control signals. Forexample, a receiving device may try multiple receive directions byreceiving via different antenna subarrays, by processing receivedsignals according to different antenna subarrays, by receiving accordingto different receive beamforming weight sets applied to signals receivedat a plurality of antenna elements of an antenna array, or by processingreceived signals according to different receive beamforming weight setsapplied to signals received at a plurality of antenna elements of anantenna array, any of which may be referred to as “listening” accordingto different receive beams or receive directions. In some examples areceiving device may use a single receive beam to receive along a singlebeam direction (e.g., when receiving a data signal). The single receivebeam may be aligned in a beam direction determined based on listeningaccording to different receive beam directions (e.g., a beam directiondetermined to have a highest signal strength, highest signal-to-noiseratio, or otherwise acceptable signal quality based on listeningaccording to multiple beam directions).

In some cases, the antennas of a base station 105 or UE 115 may belocated within one or more antenna arrays, which may support MIMOoperations, or transmit or receive beamforming. For example, one or morebase station antennas or antenna arrays may be co-located at an antennaassembly, such as an antenna tower. In some cases, antennas or antennaarrays associated with a base station 105 may be located in diversegeographic locations. A base station 105 may have an antenna array witha number of rows and columns of antenna ports that the base station 105may use to support beamforming of communications with a UE 115.Likewise, a UE 115 may have one or more antenna arrays that may supportvarious MIMO or beamforming operations.

In some cases, wireless communications system 100 may be a packet-basednetwork that operate according to a layered protocol stack. In the userplane, communications at the bearer or Packet Data Convergence Protocol(PDCP) layer may be IP-based. A Radio Link Control (RLC) layer mayperform packet segmentation and reassembly to communicate over logicalchannels. A Medium Access Control (MAC) layer may perform priorityhandling and multiplexing of logical channels into transport channels.The MAC layer may also use HARQ to provide retransmission at the MAClayer to improve link efficiency. In the control plane, the RadioResource Control (RRC) protocol layer may provide establishment,configuration, and maintenance of an RRC connection between a UE 115 anda base station 105 or core network 130 supporting radio bearers for userplane data. At the Physical layer, transport channels may be mapped tophysical channels.

In some cases, UEs 115 and base stations 105 may support retransmissionsof data to increase the likelihood that data is received successfully.HARQ feedback is one technique of increasing the likelihood that data isreceived correctly over a communication link 125. HARQ may include acombination of error detection (e.g., using a cyclic redundancy check(CRC)), forward error correction (FEC), and retransmission (e.g.,automatic repeat request (ARQ)). HARQ may improve throughput at the MAClayer in poor radio conditions (e.g., signal-to-noise conditions). Insome cases, a wireless device may support same-slot HARQ feedback, wherethe device may provide HARQ feedback in a specific slot for datareceived in a previous symbol in the slot. In other cases, the devicemay provide HARQ feedback in a subsequent slot, or according to someother time interval.

Time intervals in LTE or NR may be expressed in multiples of a basictime unit, which may, for example, refer to a sampling period ofT_(s)=1/30,720,000 seconds. Time intervals of a communications resourcemay be organized according to radio frames each having a duration of 10milliseconds (ms), where the frame period may be expressed asT_(f)=307,200 T_(s). The radio frames may be identified by a systemframe number (SFN) ranging from 0 to 1023. Each frame may include 10subframes numbered from 0 to 9, and each subframe may have a duration of1 ms. A subframe may be further divided into 2 slots each having aduration of 0.5 ms, and each slot may contain 6 or 7 modulation symbolperiods (e.g., depending on the length of the cyclic prefix prepended toeach symbol period). Excluding the cyclic prefix, each symbol period maycontain 2048 sampling periods. In some cases, a subframe may be thesmallest scheduling unit of the wireless communications system 100, andmay be referred to as a transmission time interval (TTI). In othercases, a smallest scheduling unit of the wireless communications system100 may be shorter than a subframe or may be dynamically selected (e.g.,in bursts of shortened TTIs (sTTIs) or in selected component carriersusing sTTIs).

In some wireless communications systems, a slot may further be dividedinto multiple mini-slots containing one or more symbols. In someinstances, a symbol of a mini-slot or a mini-slot may be the smallestunit of scheduling. Each symbol may vary in duration depending on thesubcarrier spacing or frequency band of operation, for example. Further,some wireless communications systems may implement slot aggregation inwhich multiple slots or mini-slots are aggregated together and used forcommunication between a UE 115 and a base station 105.

The term “carrier” refers to a set of radio frequency spectrum resourceshaving a defined physical layer structure for supporting communicationsover a communication link 125. For example, a carrier of a communicationlink 125 may include a portion of a radio frequency spectrum band thatis operated according to physical layer channels for a given radioaccess technology. Each physical layer channel may carry user data,control information, or other signaling. A carrier may be associatedwith a pre-defined frequency channel (e.g., an evolved universal mobiletelecommunication system terrestrial radio access (E-UTRA) absoluteradio frequency channel number (EARFCN)), and may be positionedaccording to a channel raster for discovery by UEs 115. Carriers may bedownlink or uplink (e.g., in an FDD mode), or be configured to carrydownlink and uplink communications (e.g., in a TDD mode). In someexamples, signal waveforms transmitted over a carrier may be made up ofmultiple sub-carriers (e.g., using multi-carrier modulation (MCM)techniques such as orthogonal frequency division multiplexing (OFDM) ordiscrete Fourier transform spread OFDM (DFT-S-OFDM)).

The organizational structure of the carriers may be different fordifferent radio access technologies (e.g., LTE, LTE-A, LTE-A Pro, NR).For example, communications over a carrier may be organized according toTTIs or slots, each of which may include user data as well as controlinformation or signaling to support decoding the user data. A carriermay also include dedicated acquisition signaling (e.g., synchronizationsignals or system information, etc.) and control signaling thatcoordinates operation for the carrier. In some examples (e.g., in acarrier aggregation configuration), a carrier may also have acquisitionsignaling or control signaling that coordinates operations for othercarriers.

Physical channels may be multiplexed on a carrier according to varioustechniques. A physical control channel and a physical data channel maybe multiplexed on a downlink carrier, for example, using time divisionmultiplexing (TDM) techniques, frequency division multiplexing (FDM)techniques, or hybrid TDM-FDM techniques. In some examples, controlinformation transmitted in a physical control channel may be distributedbetween different control regions in a cascaded manner (e.g., between acommon control region or common search space and one or more UE-specificcontrol regions or UE-specific search spaces).

A carrier may be associated with a particular bandwidth of the radiofrequency spectrum, and in some examples the carrier bandwidth may bereferred to as a “system bandwidth” of the carrier or the wirelesscommunications system 100. For example, the carrier bandwidth may be oneof a number of predetermined bandwidths for carriers of a particularradio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 MHz). Insome examples, each served UE 115 may be configured for operating overportions or all of the carrier bandwidth. In other examples, some UEs115 may be configured for operation using a narrowband protocol typethat is associated with a predefined portion or range (e.g., set ofsubcarriers or RB s) within a carrier (e.g., “in-band” deployment of anarrowband protocol type).

In a system employing MCM techniques, a resource element may consist ofone symbol period (e.g., a duration of one modulation symbol) and onesubcarrier, where the symbol period and subcarrier spacing are inverselyrelated. The number of bits carried by each resource element may dependon the modulation scheme (e.g., the order of the modulation scheme).Thus, the more resource elements that a UE 115 receives and the higherthe order of the modulation scheme, the higher the data rate may be forthe UE 115. In MIMO systems, a wireless communications resource mayrefer to a combination of a radio frequency spectrum resource, a timeresource, and a spatial resource (e.g., spatial layers), and the use ofmultiple spatial layers may further increase the data rate forcommunications with a UE 115.

Devices of the wireless communications system 100 (e.g., base stations105 or UEs 115) may have a hardware configuration that supportscommunications over a particular carrier bandwidth, or may beconfigurable to support communications over one of a set of carrierbandwidths. In some examples, the wireless communications system 100 mayinclude base stations 105 and/or UEs 115 that support simultaneouscommunications via carriers associated with more than one differentcarrier bandwidth.

Wireless communications system 100 may support communication with a UE115 on multiple cells or carriers, a feature which may be referred to ascarrier aggregation or multi-carrier operation. A UE 115 may beconfigured with multiple downlink component carriers and one or moreuplink component carriers according to a carrier aggregationconfiguration. Carrier aggregation may be used with both FDD and TDDcomponent carriers.

In some cases, wireless communications system 100 may utilize enhancedcomponent carriers (eCCs). An eCC may be characterized by one or morefeatures including wider carrier or frequency channel bandwidth, shortersymbol duration, shorter TTI duration, or modified control channelconfiguration. In some cases, an eCC may be associated with a carrieraggregation configuration or a dual connectivity configuration (e.g.,when multiple serving cells have a suboptimal or non-ideal backhaullink). An eCC may also be configured for use in unlicensed spectrum orshared spectrum (e.g., where more than one operator is allowed to usethe spectrum). An eCC characterized by wide carrier bandwidth mayinclude one or more segments that may be utilized by UEs 115 that arenot capable of monitoring the whole carrier bandwidth or are otherwiseconfigured to use a limited carrier bandwidth (e.g., to conserve power).

In some cases, an eCC may utilize a different symbol duration than othercomponent carriers, which may include use of a reduced symbol durationas compared with symbol durations of the other component carriers. Ashorter symbol duration may be associated with increased spacing betweenadjacent subcarriers. A device, such as a UE 115 or base station 105,utilizing eCCs may transmit wideband signals (e.g., according tofrequency channel or carrier bandwidths of 20, 40, 60, 80 MHz, etc.) atreduced symbol durations (e.g., 16.67 microseconds). A TTI in eCC mayconsist of one or multiple symbol periods. In some cases, the TTIduration (that is, the number of symbol periods in a TTI) may bevariable.

Wireless communications system 100 may be an NR system that may utilizeany combination of licensed, shared, and unlicensed spectrum bands,among others. The flexibility of eCC symbol duration and subcarrierspacing may allow for the use of eCC across multiple spectrums. In someexamples, NR shared spectrum may increase spectrum utilization andspectral efficiency, specifically through dynamic vertical (e.g., acrossthe frequency domain) and horizontal (e.g., across the time domain)sharing of resources.

A base station 105 may transmit a downlink control transmission andmultiple downlink data transmissions to a UE 115. The UE 115 maydetermine resources for an uplink data transmission based on thedownlink control transmission and may determine resources fortransmission acknowledgement messages based on the multiple downlinkdata transmissions. The UE 115 may identify that the scheduled uplinkdata transmission overlaps with the scheduled transmissionacknowledgement messages. The UE 115 may generate one or moreacknowledgement codebooks (e.g., HARQ-ACK codebooks) for transmission ofthe multiple transmission acknowledgment messages and may multiplex theone or more acknowledgement codebooks with the uplink data transmissionon the uplink data channel.

In some cases, the UE 115 may multiplex the one or more acknowledgementcodebooks based on determining that a set of timing thresholds aresatisfied by an earliest of the multiple transmission acknowledgementmessages and the uplink data transmission with respect to a latestdownlink data transmission acknowledged by one of the multipletransmission acknowledgement messages and a downlink control channeltransmission that schedules uplink transmissions for the slot.Additionally or alternatively, the UE 115 may multiplex the one or moreacknowledgement codebooks based on determining whether downlink controlinformation scheduling one or more downlink data transmissions isreceived after the downlink control transmission that schedules theuplink transmissions for the slot.

In some cases, generating the one or more acknowledgement codebooks mayinvolve separately encoding each of the multiple transmissionacknowledgement messages to corresponding coded acknowledgementcodebooks, where the corresponding acknowledgement codebooks may bemapped to the uplink data channel. Alternatively, generating the one ormore acknowledgement codebooks may involve jointly encoding the multipletransmission acknowledgement messages to a single coded acknowledgementcodebook, where the single coded acknowledgement codebook is mapped tothe uplink data channel. In either case, the UE 115 may determine anumber of bits to insert into a set of separate acknowledgementcodebooks or into a concatenation of the set of separate acknowledgementcodebooks to form the corresponding coded acknowledgement codebooks orthe single coded acknowledgement codebook. The UE 115 may determine thenumber of bits based on an uplink DAI and one or more downlink DAIs.

In this way, UE 115 may, at least in some cases, be able to handlecollisions between multiple HARQ-ACK transmissions over resourcesdetermined by the UE 115 and an overlapping PUSCH transmission overresources determined by the UE 115. If the UE 115 were not enabled tohandle such collisions, the UE 115 could end up dropping most of theHARQ-ACK information, thus leading to otherwise unnecessaryretransmissions by the base station 105. For example, in some systems, aUE might only be enabled to multiplex a single HARQ-ACK transmissionwith a PUSCH transmission. However, in wireless communications system100, UE 115 is enabled to piggyback multiple HARQ-ACK transmissions ontoa PUSCH such that the HARQ-ACK information is not lost.

FIG. 2 illustrates an example of a wireless communications system 200that supports handling collisions between multiple acknowledgementtransmissions and an uplink data transmission in accordance with aspectsof the present disclosure. In some examples, wireless communicationssystem 200 may implement aspects of wireless communications system 100.For instance, wireless communications system may include UE 115-a andbase station 105-a, which may be examples of a UE 115 and a base station105, respectively, as described with reference to FIG. 1.

Base station 105-a may transmit downlink and uplink grants to UE 115-ascheduling one or more transmissions for UE 115-a. For instance, if basestation 105-a transmits a downlink grant, UE 115-a may determineresources for receiving a PDSCH transmission from the downlink grant andif base station 105-a transmits an uplink grant, UE 115-a may determineresources for transmitting a PUSCH transmission from the uplink grant.The indication of downlink and uplink grants may be included within DCI(e.g., a downlink grant may be indicated via downlink DCI and an uplinkgrant may be indicated via uplink DCI).

After receiving a downlink DCI scheduling one or more PDSCHtransmissions, UE 115-a may transmit one or more HARQ-ACKs to basestation 105-a indicating whether UE 115-a correctly decoded the one ormore PDSCH transmissions. In one example, UE 115-a may transmit atransmission over a PUCCH resource 210 to base station 105-a indicatinga HARQ-ACK for each of the one or more PDSCH transmissions. If aparticular one of the one or more PDSCH transmissions was correctlydecoded, the PUCCH transmission may contain an ACK for the particularone of the one or more PDSCH transmissions and if the particular one ofthe one or more PDSCH transmissions was not properly decoded, the PUCCHtransmission may contain a NACK for the particular one of the one ormore PDSCH transmissions.

In general, the PUCCH transmission may indicate the HARQ-ACKs in theform of a HARQ-ACK codebook. An acknowledgement payload size of theHARQ-ACK codebook may be indicated by a downlink assignment indication(DAI) field of a downlink DCI scheduling the one or more PDSCHtransmissions (e.g., a downlink DAI). UE 115-a may generate a HARQ-ACKcodebook with the indicated payload size, may encode the HARQ-ACKcodebook, and may transmit the HARQ-ACK codebook in the PUCCHtransmission.

However, in some cases, UE 115-a may receive an uplink grant schedulinga PUSCH transmission (e.g., over a PUSCH resource 205) that collides intime (e.g., has overlapping time resources) with a PUCCH resource 210for transmitting a HARQ-ACK codebook. In such cases, UE 115-a maypiggyback the HARQ-ACK codebook on the PUSCH transmission. For instance,UE 115-a may include the HARQ-ACK codebook or a modified version of theHARQ-ACK codebook (e.g., a version with dummy NACK bits) in the PUSCHtransmission. The uplink grant may include an uplink DCI containing anuplink DAI field. Upon receiving the uplink DCI, UE 115-a may determinewhether the payload size indicated by the downlink DAI indicated in thedownlink DCI agrees with or is otherwise equivalent to the payload sizeindicated by the uplink DAI. If the uplink and downlink DAI payloadsizes agree (e.g., are equal), UE 115-a may transmit the HARQ-ACKcodebook in the PUSCH using the current codebook size. If the uplink anddownlink DAI do not agree (e.g., are not equal), UE 115-a may pad dummyNACK bits at the end of the HARQ-ACK codebook until the total sizematches the uplink DAI and may transmit the HARQ-ACK codebook with thedummy NACK bits in the PUSCH transmission.

UE 115-a may determine the number of dummy NACK bits to add based on arelationship between the uplink DAI and the downlink DAI. In oneexample, the uplink and downlink DAIS may be indicated with a samenumber of bits N, where N may equal a positive integer (e.g., N=2). Thenumber of bits N may map to 2^(N) values (e.g., if N=2, there may be 4values). If the downlink DAI maps to a value P (e.g., P=3) of the 2^(N)and the uplink DAI maps to a value Q (e.g., Q=3) of the 2^(N), thenumber of inserted dummy NACK bits may be equal to (Q−P) mod (M), whereM may be equal to 2^(N) or may be equal to an integer valueindependently of 2^(N) (e.g., may equal 4, regardless of N). Forinstance, if P=2, Q=3, and M=4 then the number of inserted dummy NACKbits may be equal to (3−2) mod 4=1 mod 4=1 dummy NACK. In anotherexample, if P=3, Q=2, and M=4, then the number of inserted dummy NACKbits may be equal to (2−3) mod 4=(−1) mod 4=3 dummy NACK bits inserted.

In other cases, UE 115-a may determine resources for a PUSCHtransmission (e.g., a PUSCH resource 205) that collides in time withmultiple PUCCH resources 210 for transmitting HARQ-ACKs. Such collisionsmay occur if UE 115-a transmits multiple HARQ-ACK transmissions in aslot (e.g., transmits multiple HARQ-ACK transmissions per slot). Forinstance, in the present example, PUSCH resource 205-a and PUCCHresources 210-a, 210-b, and 210-c may span a single slot (e.g., theremay be 3 HARQ-ACK transmissions transmitted within a single slot).

Additionally or alternatively, such collisions may occur if a slotlength for PUCCH transmissions is smaller than a slot length for PUSCHtransmissions. The slot length of a PUCCH transmission (e.g., over PUCCHresource 210) may be smaller than the slot length for a PUSCHtransmission (e.g., over PUSCH resource 205) if the transmissions occuron different carriers, and the PUSCH carrier may have a lowersub-carrier spacing (SCS) than the PUCCH carrier. In such cases, two ormore slots overlapping a slot containing the PUSCH may contain PUCCHtransmissions with HARQ-ACKs. For instance, in the present example,PUSCH resource 205-a may span a single slot within the carriercontaining PUSCH resource 205-a and each PUCCH resource 210 may span asingle slot within the carrier containing the PUCCH resources 210.However, the slot size associated with PUSCH resource 205-a may belarger than the slot size associated PUCCH resources 210. As such, evenif PUCCH resources 210-a, 210-b, and 210-c each span a single slot oftheir carrier, multiple PUCCH resources 210 may overlap in time withPUSCH resource 205-a.

In either case, to resolve collisions between multiple HARQ-ACKtransmissions over PUCCH resources 210 and the PUSCH transmission overPUSCH resource 205-a, UE 115-a may piggyback the HARQ-ACK codebooksassociated with the multiple PUCCH resources 210 to the PUSCHtransmission. In some cases, UE 115-a may combine the codebooks if themultiple HARQ-ACK feedback and the PUSCH are associated with traffic ofthe same type (e.g., all are associated with ultra-reliable low-latencycommunication (URLLC) traffic, or all are associated with enhancedmobile broadband (eMBB) traffic). Generally, the uplink grant mayinclude an uplink DCI with a single uplink DAI. As such, UE 115-a maydetermine how to insert dummy NACK bits into HARQ-ACK codebooksassociated with each PUCCH resource 210 scheduled for a HARQ-ACKtransmission or into the concatenated codebook based on the singleuplink DAI.

In one example, UE 115-a may separately encode each of the HARQ-ACKcodebooks and may map them sequentially to the PUSCH transmission ofPUSCH resource 205-a. For instance UE 115-a may generate multipleHARQ-ACK codebooks and may then encode each of the multiple HARQ-ACKcodebooks separately. In such cases, the uplink DAI of the uplink DCI inthe uplink grant for the PUSCH transmission may indicate HARQ-ACKcodebook sizes for each of the PUCCH resources 210 associated withHARQ-ACK transmissions prior to performing separate encoding. UE 115-amay use individual downlink DAI to generate each HARQ-ACK codebook andmay use the uplink DAI to insert dummy NACK bits into each codebook. Forinstance, a downlink DCI scheduling a HARQ-ACK transmission on PUCCHresource 210-a may indicate a DAI with a value P₁=2, a downlink DCIscheduling a HARQ-ACK transmission on PUCCH resource 210-b may indicatea DAI with a value P₂=5, and a downlink DCI scheduling a HARQ-ACKtransmission on PUCCH resource 210-c may indicate a DAI with a valueP₃=3. If the uplink DAI indicates a value Q=2 and M=4, then a HARQ-ACKcodebook generated for PUCCH resource 210-a may receive no additionaldummy NACK bits (e.g., (Q−P₁) mod (4)=(2−2) mod (4)=0 mod 4=0 bits), aHARQ-ACK codebook generated for PUCCH resource 210-b may receive 1 dummyNACK (e.g., (Q−P₂) mod (4)=(2−5) mod (4)=(−3) mod 4=1), and a HARQ-ACKcodebook generated for PUCCH resource 210-c may receive 3 dummy NACKbits (e.g., (Q−P₃) mod (4)=(2−3) mod (4)=(−1) mod 4=3). After the dummyNACK bits have been inserted, the HARQ-ACK codebook for PUCCH resource210-a may have a size 2, the HARQ-ACK codebook for PUCCH resource 210-bmay have a size 6, and the HARQ-ACK codebook for PUCCH resource 210-cmay have a size 6. Upon inserting the dummy NACK bits, the threeHARQ-ACK codebooks may be separately encoded and may be mappedsequentially to the PUSCH transmission of PUSCH resource 205-a.

In another example, UE 115-a may concatenate each of the HARQ-ACKcodebooks together first to generate a concatenated HARQ-ACK codebook;may jointly encode the concatenated HARQ-ACK codebook; and may map ormultiplex the encoded codebook to the PUSCH transmission on PUSCHresource 205-a. For instance, UE 115-a may concatenate a HARQ-ACKcodebook generated for PUCCH resource 210-a, a HARQ-ACK codebookgenerated for PUCCH resource 210-b, and a HARQ-ACK codebook generatedfor PUCCH resource 210-c. In such cases, the uplink DAI of the uplinkDCI in the uplink grant for the PUSCH transmission may indicate HARQ-ACKcodebook sizes for each of the multiple HARQ-ACK transmissions prior toconcatenation. For instance, a downlink DCI scheduling a HARQ-ACKtransmission over PUCCH resource 210-a may indicate a downlink DAI witha value P₁=2, a downlink DCI scheduling a HARQ-ACK transmission overPUCCH resource 210-b may indicate a DAI with a value P₂=5, and adownlink DCI scheduling a HARQ-ACK transmission over PUCCH resource210-c may indicate a DAI with a value P₃=3. If the uplink DAI indicatesa value Q=2 and M=4, then a HARQ-ACK codebook generated for PUCCHresource 210-a may receive no additional dummy NACK bits (e.g., (Q−P₁)mod (4)=(2−2) mod (4)=0 mod 4=0 bits), a HARQ-ACK codebook generated forPUCCH resource 210-b may receive 1 dummy NACK (e.g., (Q−P₂) mod(4)=(2−5) mod (4)=(−3) mod 4=1), and a HARQ-ACK codebook generated forPUCCH resource 210-c may receive 3 dummy NACK bits (e.g., (Q−P₃) mod(4)=(2−3) mod (4)=(−1) mod 4=3). After the dummy NACK bits have beeninserted, the HARQ-ACK codebook for PUCCH resource 210-a may have a size2, the HARQ-ACK codebook for PUCCH resource 210-b may have a size 6, andthe HARQ-ACK codebook for PUCCH resource 210-c may have a size 6. Afterinserting the dummy NACK bits, UE 115-b may concatenate the threeHARQ-ACK codebooks, which may have a combined size equal to a sum of thesize each of the three HARQ-ACK codebooks (e.g., the concatenated ormultiplexed codebook may have a size equal to 2+6+6=14 bits). Theconcatenated codebook may be jointly encoded and may be mapped ormultiplexed to the PUSCH transmission over PUSCH resource 205-a.

Alternatively, the uplink DAI of the uplink DCI in the uplink grant forthe PUSCH transmission may indicate the total HARQ-ACK codebook sizeafter concatenation. In such cases, UE 115-a may first generate themultiple HARQ-ACK codebooks according to the individual downlink DAI foreach codebook. UE 115-a may then concatenate the multiple HARQ-ACKcodebooks and may accumulate the downlink DAIs. If the accumulateddownlink DAI does not match the uplink DAI, UE 115-a may pad dummy NACKbits. For instance, a downlink DCI scheduling a HARQ-ACK transmission onPUCCH resource 210-a may indicate a DAI with a value P₁=2, a downlinkDCI scheduling a HARQ-ACK transmission on PUCCH resource 210-b mayindicate a DAI with a value P₂=5, and a downlink DCI scheduling aHARQ-ACK transmission on PUCCH resource 210-c may indicate a DAI with avalue P₃=3. UE 115-a may concatenate the codebooks associated with thetransmissions and may combine the DAI values to determine a total valueP_(T) (e.g., P_(T)=P₁+P₂+P₃=2+5+3=11 bits). UE 115-a may then insert anumber of dummy NACK bits according to P_(T), Q, and M. For instance,assuming that M=4, UE 115-a may insert 3 dummy NACK bits (e.g.,(Q−P_(T)) mod (4)=(2−11) mod (4)=(−9) mod (4)=3) into the concatenatedcodebook. After inserting the 3 dummy NACK bits, the concatenatedcodebook may have a size of 14 bits. The concatenated codebook may bejointly encoded and mapped to the PUSCH transmission over PUSCH resource205-a.

In some examples, base station 105-a may perform scheduling such thatmultiple HARQ-ACKs and/or multiple PUCCH resources 210 do not overlapwith a PUSCH resource 205. For instance, base station 105-a may performthe scheduling in such a way that only one HARQ-ACK overlaps with aPUSCH resource 205.

On average, using uplink DAI to indicate total size may cause fewerdummy NACK bits to be inserted into a concatenated codebook than usingthe uplink DAI to indicate individual codebook size. Alternatively,using uplink DAI to indicate individual codebook size may ensure thateach codebook is decoded correctly at base station 105-a, as basestation 105-a may be aware that each codebook is the same size and maybe able to parse and/or decode the codebooks accordingly.

FIG. 3 illustrates an example of an acknowledgement multiplexing scheme300 that supports handling collisions between multiple acknowledgementtransmissions and an uplink data transmission in accordance with aspectsof the present disclosure. Downlink DCI 305-a may be a downlink grant(e.g., PDCCH) that schedules resources for receiving a PDSCHtransmission over PDSCH resource 310-a. A UE 115 may determine to usePUCCH resource 325-a for transmitting one or more HARQ-ACKs for PDSCHresource 310-a in a HARQ-ACK codebook. Downlink DCI 305-b may be adownlink grant that schedules resources for receiving a PDSCHtransmission over PDSCH resource 310-b. The UE 115 may determine to usePUCCH resource 325-b for transmitting one or more HARQ-ACKs for PDSCHresource 310-b in a HARQ-ACK codebook. Uplink DCI 315 may be an uplinkgrant that schedules resources for transmitting a PUSCH transmissionover PUSCH resource 320.

In some cases, a UE 115 may multiplex all uplink control information(UCI) (e.g., the HARQ-ACK codebooks associated with PUCCH resources325-a and 325-b) on a HARQ-ACK transmission over a PUCCH resource 325 ora PUSCH transmission over a PUSCH resource 320 (e.g., as described withreference to FIG. 2). In some cases, the UE 115 may perform themultiplexing if one or both of the following timeline conditions issatisfied. The first timeline condition may be that the first symbol ofthe earliest PUCCH resource 325 (e.g., PUCCH resource 325-a) or PUSCHresource 320, whichever is earlier, among the overlapping channelsstarts no earlier than symbol N₁+X after the last symbol of a latestPDSCH (e.g., PDSCH resource 310-b) associated with the set ofoverlapping PUCCH resources 325-a. The time spanned by N₁+X may beconsidered a first timing threshold. The second condition may be thatthe first symbol of the earliest PUCCH resource 325 (e.g., PUCCHresource 325-b) or the PUSCH transmission of PUSCH resource 320,whichever is earlier, among the overlapping channels starts no earlierthan N₂+Y symbols after the last symbol of the latest uplink grant(e.g., uplink DCI 315) scheduling uplink transmissions for HARQ-ACK(e.g., over PUCCH resources 325) and/or PUSCH transmission (e.g., overPUSCH resource 320) for the slot containing the PUSCH resource 320. Thetime spanned by N₂+Y may be considered a second timing threshold. If oneor both of these conditions is not satisfied, the UE 115 may determinean error case.

Additionally or alternatively, the UE 115 may multiplex all UCI on aHARQ-ACK transmission over a PUCCH resource 325 or a PUSCH transmissionover a PUSCH resource 320 (e.g., as described with reference to FIG. 2)if all downlink DCIs 305 arrive no later than the uplink DCI 315scheduling the PUSCH transmission over the PUSCH resource 320. If one ormore downlink DCIs 305 arrive after the uplink DCI 315, the UE 115 maydetermine an error case or may discard HARQ-ACK that corresponds to anydownlink DCI 305 arriving after the uplink DCI 315. The base station 105may schedule later HARQ-ACKs not overlapping with the PUSCH resource320. In some cases, the UE 115 may perform multiplexing if the timelineconditions are satisfied and the downlink DCIs 305 for the slot arriveno later than the uplink DCI 315 scheduling the PUSCH transmission forPUSCH resource 320.

FIG. 4 illustrates an example of a process flow 400 that supportshandling collisions between multiple acknowledgement transmissions andan uplink data transmission in accordance with aspects of the presentdisclosure. In some examples, process flow 400 may implement aspects ofwireless communications system 100. For instance, wirelesscommunications system may include UE 115-b and base station 105-b, whichmay be examples of a UE 115 and a base station 105, respectively, asdescribed with reference to FIG. 1.

At 405, base station 105-b may transmit a downlink control transmission(e.g., a PDCCH transmission containing a downlink DCI). The downlinkcontrol transmission may schedule an uplink transmission (e.g., anuplink data transmission, such as a PUSCH) by UE 115-b during a slot. UE115-b may receive the downlink control transmission. In some cases, thedownlink control transmission may include a single indication ofacknowledgement payload size.

At 410, base station 105-b may transmit multiple downlink datatransmissions (e.g., PDSCH transmissions) to be acknowledged by UE 115-bvia corresponding multiple transmission acknowledgement messages (e.g.,HARQ-ACK) and which may be scheduled to at least partially overlap intime with the uplink data transmissions. UE 115-b may receive themultiple downlink data transmissions. In some cases, the multipledownlink data transmissions may be scheduled by previously receiveddownlink control transmissions (e.g., PDCCH transmissions includingDCI). In some cases, the previously received downlink control channeltransmissions may include a set of indications of acknowledgementpayload size. Each of the set of indications may correspond to one ofthe multiple transmission acknowledgement messages.

At 415, UE 115-b may identify that an uplink data transmission (e.g.,the uplink data transmission scheduled by the downlink controltransmission) scheduled for transmission by UE 115-b in a slot overlapswith multiple transmission acknowledgement messages also scheduled by UE115-b. The multiple transmission acknowledgement messages may bescheduled to be transmitted over uplink control channel resources (e.g.,PUCCH resources). In some cases, the multiple transmissionacknowledgement messages may be scheduled to be transmitted via separatePUCCH transmissions within the slot. In other cases, the multipletransmission acknowledgement messages may be scheduled to be transmittedon a first carrier that has a higher sub-carrier spacing than that of asecond carrier used by the uplink data transmission. In such cases, themultiple transmission acknowledgement messages may be scheduled to betransmitted via separate PUCCH transmissions within corresponding slotsof the first carrier. In some cases, the multiple transmissionacknowledgement messages and the uplink data transmission may beassociated with the same traffic type. The same traffic type may be, forinstance, URLLC traffic or may be eMBB traffic.

At 420, UE 115-b may determine that a set of timing thresholds aresatisfied by an earliest of the multiple transmission acknowledgementmessages and the uplink data transmission with respect to a latestdownlink data transmission acknowledged by one of the multipletransmission acknowledgement messages and a downlink control channeltransmission that schedules uplink transmissions for the slot. Forinstance, UE 115-b may determine that a first timing threshold issatisfied by the earliest of the multiple transmission acknowledgementmessages and the uplink data transmission being at least a firstpredetermined number of symbols (e.g., N₁+X symbols, as described withreference to FIG. 3) after a last symbol of the latest downlink datatransmission acknowledged by one of the multiple transmissionacknowledgement messages. Additionally or alternatively, UE 115-b maydetermine that a second timing threshold is satisfied by the earliest ofthe multiple transmission acknowledgement messages and the uplink datatransmission being at least a second predetermined number of symbols(e.g., N₂+Y symbols, as described with reference to FIG. 3) after a lastsymbol of the downlink control channel transmission that schedulesuplink transmissions for the slot.

At 425, UE 115-b may generate one or more acknowledgement codebooks(e.g., HARQ-ACK codebooks) for transmission of the multiple transmissionacknowledgement messages. In some cases, generating the one or moreacknowledgement codebooks may involve separately encoding each of themultiple transmission acknowledgement messages, which may also bereferred to as feedback messages, to corresponding coded acknowledgementcodebooks, where the corresponding coded acknowledgement codebooks maybe mapped to the uplink data channel. For instance, UE 115-b maygenerate multiple unencoded acknowledgement codebooks from the multipletransmission acknowledgement messages and then may encode the multipleunencoded acknowledgement codebooks to generate the corresponding codedacknowledgement codebooks. Alternatively, generating the one or moreacknowledgement codebooks may involve jointly encoding the multipletransmission acknowledgement messages to a single coded acknowledgementcodebook, where the single coded acknowledgement codebook is mapped tothe uplink data channel.

When receiving the set of indications as described with reference to410, UE 115-b may generate a separate acknowledgement codebook for eachof the multiple transmission acknowledgement messages. UE 115-b maygenerate the separate acknowledgement codebook based on the set ofindications. Additionally, when receiving the indication ofacknowledgement payload size at 405, UE 115-b may apply the indicationto each of the separate acknowledgement codebooks to generate a set ofupdated acknowledgement codebooks for multiplexing the one or moreacknowledgement codebooks with the uplink data transmission. UE 115-bmay concatenate each of the set of updated acknowledgement codebooksprior to multiplexing the one or more acknowledgement codebooks with theuplink data transmission. Alternatively, after generating the separateacknowledgement codebooks, UE 115-b may concatenate the separateacknowledgement codebooks for each of the multiple transmissionacknowledgement messages. In such cases, UE 115-b may apply the secondindication to the concatenated acknowledgement codebooks to generate asingle updated acknowledgement codebook for multiplexing the one or moreacknowledgement codebooks with the uplink data transmission.

At 430, UE 115-b may multiplex the one or more acknowledgement codebookswith the uplink data transmission on an uplink data channel (e.g., aPUSCH). In some cases, UE 115-b may multiplex the one or moreacknowledgement codebooks with the uplink data transmission based on theset of timing thresholds being satisfied and/or based on determiningthat DCI scheduling the downlink data transmissions is received beforethe downlink control transmission that schedules the uplinktransmissions for the slot. For instance, UE 115-b may performmultiplexing if all of the DCI with associated transmissionacknowledgement messages scheduled in the slot are received beforeuplink DCI scheduling uplink transmissions for the slot. Additionally oralternatively, if UE 115-b determines that downlink control informationscheduling one or more downlink data transmissions is received after thedownlink control transmission that schedules the uplink transmissionsfor the slot, the acknowledgement codebooks corresponding to responsetransmission acknowledgement messages associated with the one or moredownlink data transmissions received after the downlink controltransmission are not included in the multiplexing.

At 435, UE 115-b may transmit the uplink data transmission on the uplinkdata channel. Base station 105-b may receive the uplink datatransmission. Upon receiving the uplink data transmission, base station105-b may receive, from UE 115-b, one or more acknowledgement codebookscorresponding to the multiple transmission acknowledgement messages,where the one or more acknowledgement codebooks may be multiplexed withthe uplink data transmission based on the set of timing thresholds beingsatisfied.

Process flow 400, therefore, provides a method that may enable UE 115-bto multiplex multiple HARQ-ACK transmissions on a PUSCH when collisionsbetween the multiple HARQ-ACK transmissions occur with a PUSCHtransmission. Through process flow 400, UE 115-b may reduce the numberof retransmissions used by the base station 105-b arising fromunreported acknowledgement feedback. This, in turn, may result in moreefficient communications and additional power savings at the UE 115-b.

FIG. 5 shows a block diagram 500 of a device 505 that supports handlingcollisions between multiple acknowledgement transmissions and an uplinkdata transmission in accordance with aspects of the present disclosure.The device 505 may be an example of aspects of a UE 115 as describedherein. The device 505 may include a receiver 510, a communicationsmanager 515, and a transmitter 520. The device 505 may also include aprocessor. Each of these components may be in communication with oneanother (e.g., via one or more buses).

The receiver 510 may receive information such as packets, user data, orcontrol information associated with various information channels (e.g.,control channels, data channels, and information related to handlingcollisions between multiple acknowledgement transmissions and an uplinkdata transmission, etc.). Information may be passed on to othercomponents of the device 505. The receiver 510 may be an example ofaspects of the transceiver 820 described with reference to FIG. 8. Thereceiver 510 may utilize a single antenna or a set of antennas.

The communications manager 515 may identify that an uplink datatransmission scheduled in a slot overlaps with multiple scheduledtransmission acknowledgement messages, determine that a set of timingthresholds are satisfied by an earliest of the multiple scheduledtransmission acknowledgement messages and the uplink data transmissionwith respect to a latest downlink data transmission acknowledged by oneof the multiple scheduled transmission acknowledgement messages and adownlink control transmission that schedules the uplink datatransmission, generate one or more acknowledgement codebooks fortransmission of the multiple scheduled transmission acknowledgementmessages, and multiplex, based on the set of timing thresholds beingsatisfied, the one or more acknowledgement codebooks with the uplinkdata transmission on an uplink data channel. The communications manager515 may be an example of aspects of the communications manager 810described herein.

The communications manager 515, or its sub-components, may beimplemented in hardware, code (e.g., software or firmware) executed by aprocessor, or any combination thereof. If implemented in code executedby a processor, the functions of the communications manager 515, or itssub-components may be executed by a general-purpose processor, a digitalsignal processor (DSP), an application-specific integrated circuit(ASIC), a field-programmable gate array (FPGA) or other programmablelogic device, discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed in the present disclosure.

The communications manager 515, or its sub-components, may be physicallylocated at various positions, including being distributed such thatportions of functions are implemented at different physical locations byone or more physical components. In some examples, the communicationsmanager 515, or its sub-components, may be a separate and distinctcomponent in accordance with various aspects of the present disclosure.In some examples, the communications manager 515, or its sub-components,may be combined with one or more other hardware components, includingbut not limited to an input/output (I/O) component, a transceiver, anetwork server, another computing device, one or more other componentsdescribed in the present disclosure, or a combination thereof inaccordance with various aspects of the present disclosure.

The transmitter 520 may transmit signals generated by other componentsof the device 505. In some examples, the transmitter 520 may becollocated with a receiver 510 in a transceiver module. For example, thetransmitter 520 may be an example of aspects of the transceiver 820described with reference to FIG. 8. The transmitter 520 may utilize asingle antenna or a set of antennas.

FIG. 6 shows a block diagram 600 of a device 605 that supports handlingcollisions between multiple acknowledgement transmissions and an uplinkdata transmission in accordance with aspects of the present disclosure.The device 605 may be an example of aspects of a device 505, or a UE 115as described herein. The device 605 may include a receiver 610, acommunications manager 615, and a transmitter 640. The device 605 mayalso include a processor. Each of these components may be incommunication with one another (e.g., via one or more buses).

The receiver 610 may receive information such as packets, user data, orcontrol information associated with various information channels (e.g.,control channels, data channels, and information related to handlingcollisions between multiple acknowledgement transmissions and an uplinkdata transmission, etc.). Information may be passed on to othercomponents of the device 605. The receiver 610 may be an example ofaspects of the transceiver 820 described with reference to FIG. 8. Thereceiver 610 may utilize a single antenna or a set of antennas.

The communications manager 615 may be an example of aspects of thecommunications manager 515 as described herein. The communicationsmanager 615 may include an uplink data transmission identifier 620, atiming threshold satisfaction determiner 625, an acknowledgementcodebook generator 630, and an acknowledgement codebook multiplexer 635.The communications manager 615 may be an example of aspects of thecommunications manager 810 described herein.

The uplink data transmission identifier 620 may identify that an uplinkdata transmission scheduled in a slot overlaps with multiple scheduledtransmission acknowledgement messages.

The timing threshold satisfaction determiner 625 may determine that aset of timing thresholds are satisfied by an earliest of the multiplescheduled transmission acknowledgement messages and the uplink datatransmission with respect to a latest downlink data transmissionacknowledged by one of the multiple scheduled transmissionacknowledgement messages and a downlink control transmission thatschedules the uplink data transmission.

The acknowledgement codebook generator 630 may generate one or moreacknowledgement codebooks for transmission of the multiple scheduledtransmission acknowledgement messages.

The acknowledgement codebook multiplexer 635 may multiplex, based on theset of timing thresholds being satisfied, the one or moreacknowledgement codebooks with the uplink data transmission on an uplinkdata channel.

The transmitter 640 may transmit signals generated by other componentsof the device 605. In some examples, the transmitter 640 may becollocated with a receiver 610 in a transceiver module. For example, thetransmitter 640 may be an example of aspects of the transceiver 820described with reference to FIG. 8. The transmitter 640 may utilize asingle antenna or a set of antennas.

FIG. 7 shows a block diagram 700 of a communications manager 705 thatsupports handling collisions between multiple acknowledgementtransmissions and an uplink data transmission in accordance with aspectsof the present disclosure. The communications manager 705 may be anexample of aspects of a communications manager 515, a communicationsmanager 615, or a communications manager 810 described herein. Thecommunications manager 705 may include an uplink data transmissionidentifier 710, a timing threshold satisfaction determiner 715, anacknowledgement codebook generator 720, an acknowledgement codebookmultiplexer 725, a transmission acknowledgement message encoder 730, andan acknowledgement payload size indicator 735. Each of these modules maycommunicate, directly or indirectly, with one another (e.g., via one ormore buses).

The uplink data transmission identifier 710 may identify that an uplinkdata transmission scheduled in a slot overlaps with multiple scheduledtransmission acknowledgement messages. In some cases, the multiplescheduled transmission acknowledgement messages are each scheduled to betransmitted via separate physical uplink control channel transmissionswithin the slot. In some cases, the multiple scheduled transmissionacknowledgement messages are scheduled to be transmitted on a firstcarrier that has a higher sub-carrier spacing than that of a secondcarrier used by the uplink data transmission, and where the multiplescheduled transmission acknowledgement messages are each scheduled to betransmitted via separate physical uplink control channel transmissionswithin corresponding slots of the first carrier. In some cases, themultiple scheduled transmission acknowledgement messages and the uplinkdata transmission are each associated with a same traffic type. In somecases, the same traffic type is ultra-reliable low-latencycommunications traffic. In some cases, the same traffic type is enhancedmobile broadband traffic.

The timing threshold satisfaction determiner 715 may determine that aset of timing thresholds are satisfied by an earliest of the multiplescheduled transmission acknowledgement messages and the uplink datatransmission with respect to a latest downlink data transmissionacknowledged by one of the multiple scheduled transmissionacknowledgement messages and a downlink control transmission thatschedules the uplink data transmission. In some examples, the timingthreshold satisfaction determiner 715 may determine that a first timingthreshold is satisfied by the earliest of the multiple scheduledtransmission acknowledgement messages and the uplink data transmissionbeing at least a first predetermined number of symbols after a lastsymbol of the latest downlink data transmission acknowledged by one ofthe multiple transmission acknowledgment messages. In some examples, thetiming threshold satisfaction determiner 715 may determine that a secondtiming threshold is satisfied by the earliest of the multiple scheduledtransmission acknowledgement messages and the uplink data transmissionbeing at least a second predetermined number of symbols after a lastsymbol of the downlink control transmission that schedules uplinktransmissions for the slot.

The acknowledgement codebook generator 720 may generate one or moreacknowledgement codebooks for transmission of the multiple scheduledtransmission acknowledgement messages. In some examples, theacknowledgement codebook generator 720 may generate a separateacknowledgement codebook for each of the multiple scheduled transmissionacknowledgement messages based on respective ones of the set of firstindications. In some examples, the acknowledgement codebook generator720 may pad at least one or more of the separate acknowledgementcodebooks according to the single second indication to generate a set ofupdated acknowledgement codebooks for multiplexing the one or moreacknowledgement codebooks with the uplink data transmission. In someexamples, the acknowledgement codebook generator 720 may concatenateeach of the set of updated acknowledgement codebooks prior tomultiplexing the one or more acknowledgement codebooks with the uplinkdata transmission. In some examples, the acknowledgement codebookgenerator 720 may generate a separate acknowledgement codebook for eachof the multiple scheduled transmission acknowledgement messages based onrespective ones of the set of first indications. In some examples, theacknowledgement codebook generator 720 may concatenate the separateacknowledgement codebooks for each of the multiple scheduledtransmission acknowledgement messages. In some examples, theacknowledgement codebook generator 720 may apply the single secondindication to the concatenated acknowledgement codebooks to generate asingle updated acknowledgement codebook for multiplexing the one or moreacknowledgement codebooks with the uplink data transmission.

The acknowledgement codebook multiplexer 725 may multiplex, based on theset of timing thresholds being satisfied, the one or moreacknowledgement codebooks with the uplink data transmission on an uplinkdata channel. In some examples, the acknowledgement codebook multiplexer725 may determine that downlink control information scheduling downlinkdata transmissions is received before the downlink control transmissionthat schedules the uplink transmissions for the slot, where multiplexingthe one or more acknowledgement codebooks with the uplink datatransmission is further based on the downlink control information beingreceived before the downlink control transmission. In some examples, theacknowledgement codebook multiplexer 725 may determine that downlinkcontrol information scheduling one or more downlink data transmissionsis received after the downlink control transmission that schedules theuplink transmissions for the slot, where acknowledgement codebookscorresponding to responsive transmission acknowledgement messagesassociated with the one or more downlink data transmissions receivedafter the downlink control transmission are not included in generatingthe one or more acknowledgement codebooks.

The transmission acknowledgement message encoder 730 may separatelyencode each of the multiple scheduled transmission acknowledgementmessages to corresponding coded acknowledgment codebooks, where thecorresponding acknowledgement codebooks are each mapped to the uplinkdata channel. In some examples, the transmission acknowledgement messageencoder 730 may jointly encode the multiple scheduled transmissionacknowledgement messages to a single coded acknowledgement codebook,where the single coded acknowledgement codebook is mapped to the uplinkdata channel. The acknowledgement payload size indicator 735 may receivea set of first indications of acknowledgement payload size, each of theset of first indications corresponding to one of the multiple scheduledtransmission acknowledgement messages and being received via respectivedownlink control information messages scheduling downlink datatransmissions acknowledged by the multiple scheduled transmissionacknowledgement messages. In some examples, the acknowledgement payloadsize indicator 735 may receive a single second indication ofacknowledgement payload size via the downlink control transmission thatschedules the uplink transmissions for the slot.

FIG. 8 shows a diagram of a system 800 including a device 805 thatsupports handling collisions between multiple acknowledgementtransmissions and an uplink data transmission in accordance with aspectsof the present disclosure. The device 805 may be an example of orinclude the components of device 505, device 605, or a UE 115 asdescribed herein. The device 805 may include components forbi-directional voice and data communications including components fortransmitting and receiving communications, including a communicationsmanager 810, an I/O controller 815, a transceiver 820, an antenna 825,memory 830, and a processor 840. These components may be in electroniccommunication via one or more buses (e.g., bus 845).

The communications manager 810 may identify that an uplink datatransmission scheduled in a slot overlaps with multiple scheduledtransmission acknowledgement messages, determine that a set of timingthresholds are satisfied by an earliest of the multiple scheduledtransmission acknowledgement messages and the uplink data transmissionwith respect to a latest downlink data transmission acknowledged by oneof the multiple scheduled transmission acknowledgement messages and adownlink control transmission that schedules the uplink datatransmission, generate one or more acknowledgement codebooks fortransmission of the multiple scheduled transmission acknowledgementmessages, and multiplex, based on the set of timing thresholds beingsatisfied, the one or more acknowledgement codebooks with the uplinkdata transmission on an uplink data channel.

The I/O controller 815 may manage input and output signals for thedevice 805. The I/O controller 815 may also manage peripherals notintegrated into the device 805. In some cases, the I/O controller 815may represent a physical connection or port to an external peripheral.In some cases, the I/O controller 815 may utilize an operating systemsuch as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, oranother known operating system. In other cases, the I/O controller 815may represent or interact with a modem, a keyboard, a mouse, atouchscreen, or a similar device. In some cases, the I/O controller 815may be implemented as part of a processor. In some cases, a user mayinteract with the device 805 via the I/O controller 815 or via hardwarecomponents controlled by the I/O controller 815.

The transceiver 820 may communicate bi-directionally, via one or moreantennas, wired, or wireless links as described above. For example, thetransceiver 820 may represent a wireless transceiver and may communicatebi-directionally with another wireless transceiver. The transceiver 820may also include a modem to modulate the packets and provide themodulated packets to the antennas for transmission, and to demodulatepackets received from the antennas.

In some cases, the wireless device may include a single antenna 825.However, in some cases the device may have more than one antenna 825,which may be capable of concurrently transmitting or receiving multiplewireless transmissions.

The memory 830 may include random-access memory (RAM) and read-onlymemory (ROM). The memory 830 may store computer-readable,computer-executable code 835 including instructions that, when executed,cause the processor to perform various functions described herein. Insome cases, the memory 830 may contain, among other things, a basicinput/output system (BIOS) which may control basic hardware or softwareoperation such as the interaction with peripheral components or devices.

The processor 840 may include an intelligent hardware device, (e.g., ageneral-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, anFPGA, a programmable logic device, a discrete gate or transistor logiccomponent, a discrete hardware component, or any combination thereof).In some cases, the processor 840 may be configured to operate a memoryarray using a memory controller. In other cases, a memory controller maybe integrated into the processor 840. The processor 840 may beconfigured to execute computer-readable instructions stored in a memory(e.g., the memory 830) to cause the device 805 to perform variousfunctions (e.g., functions or tasks supporting handling collisionsbetween multiple acknowledgement transmissions and an uplink datatransmission).

The code 835 may include instructions to implement aspects of thepresent disclosure, including instructions to support wirelesscommunications. The code 835 may be stored in a non-transitorycomputer-readable medium such as system memory or other type of memory.In some cases, the code 835 may not be directly executable by theprocessor 840 but may cause a computer (e.g., when compiled andexecuted) to perform functions described herein.

FIG. 9 shows a block diagram 900 of a device 905 that supports handlingcollisions between multiple acknowledgement transmissions and an uplinkdata transmission in accordance with aspects of the present disclosure.The device 905 may be an example of aspects of a base station 105 asdescribed herein. The device 905 may include a receiver 910, acommunications manager 915, and a transmitter 920. The device 905 mayalso include a processor. Each of these components may be incommunication with one another (e.g., via one or more buses).

The receiver 910 may receive information such as packets, user data, orcontrol information associated with various information channels (e.g.,control channels, data channels, and information related to handlingcollisions between multiple acknowledgement transmissions and an uplinkdata transmission, etc.). Information may be passed on to othercomponents of the device 905. The receiver 910 may be an example ofaspects of the transceiver 1220 described with reference to FIG. 12. Thereceiver 910 may utilize a single antenna or a set of antennas.

The communications manager 915 may transmit, to a UE, a downlink controltransmission scheduling an uplink data transmission for the UE during aslot, transmit, to the UE, multiple downlink data transmissions that areto be acknowledged by the UE via corresponding multiple transmissionacknowledgment messages that are scheduled to at least partially overlapin time with the uplink data transmission, and receive, from the UE, oneor more acknowledgement codebooks corresponding to the multipletransmission acknowledgement messages, where the one or moreacknowledgement codebooks are multiplexed with the uplink datatransmission based on a set of timing thresholds being satisfied by anearliest of the multiple transmission acknowledgement messages and theuplink data transmission with respect to a latest downlink datatransmission of the multiple downlink data transmissions and thedownlink control transmission scheduling the uplink data transmission.The communications manager 915 may be an example of aspects of thecommunications manager 1210 described herein.

The communications manager 915, or its sub-components, may beimplemented in hardware, code (e.g., software or firmware) executed by aprocessor, or any combination thereof. If implemented in code executedby a processor, the functions of the communications manager 915, or itssub-components may be executed by a general-purpose processor, a DSP, anapplication-specific integrated circuit (ASIC), a FPGA or otherprogrammable logic device, discrete gate or transistor logic, discretehardware components, or any combination thereof designed to perform thefunctions described in the present disclosure.

The communications manager 915, or its sub-components, may be physicallylocated at various positions, including being distributed such thatportions of functions are implemented at different physical locations byone or more physical components. In some examples, the communicationsmanager 915, or its sub-components, may be a separate and distinctcomponent in accordance with various aspects of the present disclosure.In some examples, the communications manager 915, or its sub-components,may be combined with one or more other hardware components, includingbut not limited to an input/output (I/O) component, a transceiver, anetwork server, another computing device, one or more other componentsdescribed in the present disclosure, or a combination thereof inaccordance with various aspects of the present disclosure.

The transmitter 920 may transmit signals generated by other componentsof the device 905. In some examples, the transmitter 920 may becollocated with a receiver 910 in a transceiver module. For example, thetransmitter 920 may be an example of aspects of the transceiver 1220described with reference to FIG. 12. The transmitter 920 may utilize asingle antenna or a set of antennas.

FIG. 10 shows a block diagram 1000 of a device 1005 that supportshandling collisions between multiple acknowledgement transmissions andan uplink data transmission in accordance with aspects of the presentdisclosure. The device 1005 may be an example of aspects of a device905, or a base station 105 as described herein. The device 1005 mayinclude a receiver 1010, a communications manager 1015, and atransmitter 1035. The device 1005 may also include a processor. Each ofthese components may be in communication with one another (e.g., via oneor more buses).

The receiver 1010 may receive information such as packets, user data, orcontrol information associated with various information channels (e.g.,control channels, data channels, and information related to handlingcollisions between multiple acknowledgement transmissions and an uplinkdata transmission, etc.). Information may be passed on to othercomponents of the device 1005. The receiver 1010 may be an example ofaspects of the transceiver 1220 described with reference to FIG. 12. Thereceiver 1010 may utilize a single antenna or a set of antennas.

The communications manager 1015 may be an example of aspects of thecommunications manager 915 as described herein. The communicationsmanager 1015 may include a downlink control transmission transmitter1020, a downlink data transmission transmitter 1025, and anacknowledgement codebook receiver 1030. The communications manager 1015may be an example of aspects of the communications manager 1210described herein.

The downlink control transmission transmitter 1020 may transmit, to aUE, a downlink control transmission scheduling an uplink datatransmission for the UE during a slot.

The downlink data transmission transmitter 1025 may transmit, to the UE,multiple downlink data transmissions that are to be acknowledged by theUE via corresponding multiple transmission acknowledgment messages thatare scheduled to at least partially overlap in time with the uplink datatransmission.

The acknowledgement codebook receiver 1030 may receive, from the UE, oneor more acknowledgement codebooks corresponding to the multipletransmission acknowledgement messages, where the one or moreacknowledgement codebooks are multiplexed with the uplink datatransmission based on a set of timing thresholds being satisfied by anearliest of the multiple transmission acknowledgement messages and theuplink data transmission with respect to a latest downlink datatransmission of the multiple downlink data transmissions and thedownlink control transmission scheduling the uplink data transmission.

The transmitter 1035 may transmit signals generated by other componentsof the device 1005. In some examples, the transmitter 1035 may becollocated with a receiver 1010 in a transceiver module. For example,the transmitter 1035 may be an example of aspects of the transceiver1220 described with reference to FIG. 12. The transmitter 1035 mayutilize a single antenna or a set of antennas.

FIG. 11 shows a block diagram 1100 of a communications manager 1105 thatsupports handling collisions between multiple acknowledgementtransmissions and an uplink data transmission in accordance with aspectsof the present disclosure. The communications manager 1105 may be anexample of aspects of a communications manager 915, a communicationsmanager 1015, or a communications manager 1210 described herein. Thecommunications manager 1105 may include a downlink control transmissiontransmitter 1110, a downlink data transmission transmitter 1115, anacknowledgement codebook receiver 1120, and an acknowledgement payloadsize transmitter 1125. Each of these modules may communicate, directlyor indirectly, with one another (e.g., via one or more buses).

The downlink control transmission transmitter 1110 may transmit, to aUE, a downlink control transmission scheduling an uplink datatransmission for the UE during a slot. In some examples, the downlinkcontrol transmission transmitter 1110 may transmit a downlink controlinformation scheduling at least one of the multiple downlink datatransmissions such that the downlink control information is received atthe UE after the downlink control transmission scheduling the uplinkdata transmission, where ones of the multiple transmissionacknowledgement messages that are responsive to the at least one of themultiple downlink data transmissions are not included in the one or moreacknowledgement codebooks multiplexed with the uplink data transmissionreceived from the UE.

The downlink data transmission transmitter 1115 may transmit, to the UE,multiple downlink data transmissions that are to be acknowledged by theUE via corresponding multiple transmission acknowledgment messages thatare scheduled to at least partially overlap in time with the uplink datatransmission. In some cases, the multiple transmission acknowledgementmessages are each scheduled to be transmitted via separate physicaluplink control channel transmissions within the slot. In some cases, themultiple transmission acknowledgement messages are scheduled to betransmitted on a first carrier that has a higher sub-carrier spacingthan that of a second carrier used by the uplink data transmission, andwhere the multiple transmission acknowledgement messages are eachscheduled to be transmitted via separate physical uplink control channeltransmissions within corresponding slots of the first carrier. In somecases, the multiple transmission acknowledgement messages and the uplinkdata transmission are each associated with a same traffic type. In somecases, the same traffic type is ultra-reliable low-latencycommunications traffic. In some cases, the same traffic type is enhancedmobile broadband traffic.

The acknowledgement codebook receiver 1120 may receive, from the UE, oneor more acknowledgement codebooks corresponding to the multipletransmission acknowledgement messages, where the one or moreacknowledgement codebooks are multiplexed with the uplink datatransmission based on a set of timing thresholds being satisfied by anearliest of the multiple transmission acknowledgement messages and theuplink data transmission with respect to a latest downlink datatransmission of the multiple downlink data transmissions and thedownlink control transmission scheduling the uplink data transmission.In some examples, the acknowledgement codebook receiver 1120 may receiveone or more acknowledgement codebooks corresponding to the multipletransmission acknowledgement messages and multiplexed with the uplinkdata transmission is further based on downlink control informationscheduling the multiple downlink data transmissions being received atthe UE before the downlink control transmission scheduling the uplinkdata transmission. In some examples, the acknowledgement codebookreceiver 1120 may receive the multiple transmission acknowledgementmessages as separately encoded acknowledgement codebooks. In someexamples, the acknowledgement codebook receiver 1120 may receive themultiple transmission acknowledgement messages as a jointly encodedacknowledgement codebook. In some cases, the set of timing thresholdsinclude a first timing threshold and a second timing threshold, thefirst timing threshold being satisfied by the earliest of the multipletransmission acknowledgement messages and the uplink data transmissionbeing at least a first predetermined number of symbols after a lastsymbol of the latest downlink data transmission of the multiple downlinkdata transmissions, and the second timing threshold being satisfied bythe earliest of the multiple transmission acknowledgement messages andthe uplink data transmission being at least a second predeterminednumber of symbols after a last symbol of the downlink controltransmission scheduling the uplink data transmission.

The acknowledgement payload size transmitter 1125 may transmit a set offirst indications of acknowledgement payload size, each of the set offirst indications corresponding to one of the multiple transmissionacknowledgement messages and being transmitted via respective downlinkcontrol information messages scheduling the multiple downlink datatransmissions. In some examples, the acknowledgement payload sizetransmitter 1125 may transmit a single second indication ofacknowledgement payload size via the downlink control transmissionscheduling the uplink data transmission. In some cases, the singlesecond indication is indicative of acknowledgement payload size for eachof the one or more acknowledgement codebooks, and wherein each of theone or more acknowledgement codebooks is a coded acknowledgementcodebook. In some cases, the single second indication is indicative of asingle acknowledgement payload size for all of the one or moreacknowledgement codebooks.

FIG. 12 shows a diagram of a system 1200 including a device 1205 thatsupports handling collisions between multiple acknowledgementtransmissions and an uplink data transmission in accordance with aspectsof the present disclosure. The device 1205 may be an example of orinclude the components of device 905, device 1005, or a base station 105as described herein. The device 1205 may include components forbi-directional voice and data communications including components fortransmitting and receiving communications, including a communicationsmanager 1210, a network communications manager 1215, a transceiver 1220,an antenna 1225, memory 1230, a processor 1240, and an inter-stationcommunications manager 1245. These components may be in electroniccommunication via one or more buses (e.g., bus 1250).

The communications manager 1210 may transmit, to a UE, a downlinkcontrol transmission scheduling an uplink data transmission for the UEduring a slot, transmit, to the UE, multiple downlink data transmissionsthat are to be acknowledged by the UE via corresponding multipletransmission acknowledgment messages that are scheduled to at leastpartially overlap in time with the uplink data transmission, andreceive, from the UE, one or more acknowledgement codebookscorresponding to the multiple transmission acknowledgement messages,where the one or more acknowledgement codebooks are multiplexed with theuplink data transmission based on a set of timing thresholds beingsatisfied by an earliest of the multiple transmission acknowledgementmessages and the uplink data transmission with respect to a latestdownlink data transmission of the multiple downlink data transmissionsand the downlink control transmission scheduling the uplink datatransmission.

The network communications manager 1215 may manage communications withthe core network (e.g., via one or more wired backhaul links). Forexample, the network communications manager 1215 may manage the transferof data communications for client devices, such as one or more UEs 115.

The transceiver 1220 may communicate bi-directionally, via one or moreantennas, wired, or wireless links as described above. For example, thetransceiver 1220 may represent a wireless transceiver and maycommunicate bi-directionally with another wireless transceiver. Thetransceiver 1220 may also include a modem to modulate the packets andprovide the modulated packets to the antennas for transmission, and todemodulate packets received from the antennas.

In some cases, the wireless device may include a single antenna 1225.However, in some cases the device may have more than one antenna 1225,which may be capable of concurrently transmitting or receiving multiplewireless transmissions.

The memory 1230 may include RAM, ROM, or a combination thereof. Thememory 1230 may store computer-readable code 1235 including instructionsthat, when executed by a processor (e.g., the processor 1240) cause thedevice to perform various functions described herein. In some cases, thememory 1230 may contain, among other things, a BIOS which may controlbasic hardware or software operation such as the interaction withperipheral components or devices.

The processor 1240 may include an intelligent hardware device, (e.g., ageneral-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, anFPGA, a programmable logic device, a discrete gate or transistor logiccomponent, a discrete hardware component, or any combination thereof).In some cases, the processor 1240 may be configured to operate a memoryarray using a memory controller. In some cases, a memory controller maybe integrated into processor 1240. The processor 1240 may be configuredto execute computer-readable instructions stored in a memory (e.g., thememory 1230) to cause the device 1205 to perform various functions(e.g., functions or tasks supporting handling collisions betweenmultiple acknowledgement transmissions and an uplink data transmission).

The inter-station communications manager 1245 may manage communicationswith other base station 105, and may include a controller or schedulerfor controlling communications with UEs 115 in cooperation with otherbase stations 105. For example, the inter-station communications manager1245 may coordinate scheduling for transmissions to UEs 115 for variousinterference mitigation techniques such as beamforming or jointtransmission. In some examples, the inter-station communications manager1245 may provide an X2 interface within an LTE/LTE-A wirelesscommunication network technology to provide communication between basestations 105.

The code 1235 may include instructions to implement aspects of thepresent disclosure, including instructions to support wirelesscommunications. The code 1235 may be stored in a non-transitorycomputer-readable medium such as system memory or other type of memory.In some cases, the code 1235 may not be directly executable by theprocessor 1240 but may cause a computer (e.g., when compiled andexecuted) to perform functions described herein.

FIG. 13 shows a flowchart illustrating a method 1300 that supportshandling collisions between multiple acknowledgement transmissions andan uplink data transmission in accordance with aspects of the presentdisclosure. The operations of method 1300 may be implemented by a UE 115or its components as described herein. For example, the operations ofmethod 1300 may be performed by a communications manager as describedwith reference to FIGS. 5 through 8. In some examples, a UE may executea set of instructions to control the functional elements of the UE toperform the functions described below. Additionally or alternatively, aUE may perform aspects of the functions described below usingspecial-purpose hardware.

At 1305, the UE may identify that an uplink data transmission scheduledin a slot overlaps with multiple scheduled transmission acknowledgementmessages. The operations of 1305 may be performed according to themethods described herein. In some examples, aspects of the operations of1305 may be performed by an uplink data transmission identifier asdescribed with reference to FIGS. 5 through 8.

At 1310, the UE may determine that a set of timing thresholds aresatisfied by an earliest of the multiple scheduled transmissionacknowledgement messages and the uplink data transmission with respectto a latest downlink data transmission acknowledged by one of themultiple scheduled transmission acknowledgement messages and a downlinkcontrol transmission that schedules the uplink data transmission. Theoperations of 1310 may be performed according to the methods describedherein. In some examples, aspects of the operations of 1310 may beperformed by a timing threshold satisfaction determiner as describedwith reference to FIGS. 5 through 8.

At 1315, the UE may generate one or more acknowledgement codebooks fortransmission of the multiple scheduled transmission acknowledgementmessages. The operations of 1315 may be performed according to themethods described herein. In some examples, aspects of the operations of1315 may be performed by an acknowledgement codebook generator asdescribed with reference to FIGS. 5 through 8.

At 1320, the UE may multiplex, based on the set of timing thresholdsbeing satisfied, the one or more acknowledgement codebooks with theuplink data transmission on an uplink data channel. The operations of1320 may be performed according to the methods described herein. In someexamples, aspects of the operations of 1320 may be performed by anacknowledgement codebook multiplexer as described with reference toFIGS. 5 through 8.

FIG. 14 shows a flowchart illustrating a method 1400 that supportshandling collisions between multiple acknowledgement transmissions andan uplink data transmission in accordance with aspects of the presentdisclosure. The operations of method 1400 may be implemented by a UE 115or its components as described herein. For example, the operations ofmethod 1400 may be performed by a communications manager as describedwith reference to FIGS. 5 through 8. In some examples, a UE may executea set of instructions to control the functional elements of the UE toperform the functions described below. Additionally or alternatively, aUE may perform aspects of the functions described below usingspecial-purpose hardware.

At 1405, the UE may identify that an uplink data transmission scheduledin a slot overlaps with multiple scheduled transmission acknowledgementmessages. The operations of 1405 may be performed according to themethods described herein. In some examples, aspects of the operations of1405 may be performed by an uplink data transmission identifier asdescribed with reference to FIGS. 5 through 8.

At 1410, the UE may determine that a first timing threshold is satisfiedby the earliest of the multiple scheduled transmission acknowledgementmessages and the uplink data transmission being at least a firstpredetermined number of symbols after a last symbol of a latest downlinkdata transmission acknowledged by one of the multiple scheduledtransmission acknowledgment messages. The operations of 1410 may beperformed according to the methods described herein. In some examples,aspects of the operations of 1410 may be performed by a timing thresholdsatisfaction determiner as described with reference to FIGS. 5 through8.

At 1415, the UE may determine that a second timing threshold issatisfied by the earliest of the multiple scheduled transmissionacknowledgement messages and the uplink data transmission being at leasta second predetermined number of symbols after a last symbol of adownlink control transmission that schedules the uplink datatransmission. The operations of 1415 may be performed according to themethods described herein. In some examples, aspects of the operations of1415 may be performed by a timing threshold satisfaction determiner asdescribed with reference to FIGS. 5 through 8.

At 1420, the UE may generate one or more acknowledgement codebooks fortransmission of the multiple scheduled transmission acknowledgementmessages. The operations of 1420 may be performed according to themethods described herein. In some examples, aspects of the operations of1420 may be performed by an acknowledgement codebook generator asdescribed with reference to FIGS. 5 through 8.

At 1425, the UE may multiplex, based on the set of timing thresholdsbeing satisfied, the one or more acknowledgement codebooks with theuplink data transmission on an uplink data channel. The operations of1425 may be performed according to the methods described herein. In someexamples, aspects of the operations of 1425 may be performed by anacknowledgement codebook multiplexer as described with reference toFIGS. 5 through 8.

FIG. 15 shows a flowchart illustrating a method 1500 that supportshandling collisions between multiple acknowledgement transmissions andan uplink data transmission in accordance with aspects of the presentdisclosure. The operations of method 1500 may be implemented by a UE 115or its components as described herein. For example, the operations ofmethod 1500 may be performed by a communications manager as describedwith reference to FIGS. 5 through 8. In some examples, a UE may executea set of instructions to control the functional elements of the UE toperform the functions described below. Additionally or alternatively, aUE may perform aspects of the functions described below usingspecial-purpose hardware.

At 1505, the UE may identify that an uplink data transmission scheduledin a slot overlaps with multiple transmission acknowledgement messages.The operations of 1505 may be performed according to the methodsdescribed herein. In some examples, aspects of the operations of 1505may be performed by an uplink data transmission identifier as describedwith reference to FIGS. 5 through 8.

At 1510, the UE may determine that a first timing threshold is satisfiedby the earliest of the multiple scheduled transmission acknowledgementmessages and the uplink data transmission being at least a firstpredetermined number of symbols after a last symbol of a latest downlinkdata transmission acknowledged by one of the multiple transmissionacknowledgment messages. The operations of 1510 may be performedaccording to the methods described herein. In some examples, aspects ofthe operations of 1510 may be performed by a timing thresholdsatisfaction determiner as described with reference to FIGS. 5 through8.

At 1515, the UE may determine that a second timing threshold issatisfied by the earliest of the multiple scheduled transmissionacknowledgement messages and the uplink data transmission being at leasta second predetermined number of symbols after a last symbol of adownlink control transmission that schedules the uplink datatransmission. The operations of 1515 may be performed according to themethods described herein. In some examples, aspects of the operations of1515 may be performed by a timing threshold satisfaction determiner asdescribed with reference to FIGS. 5 through 8.

At 1520, the UE may generate one or more acknowledgement codebooks fortransmission of the multiple scheduled transmission acknowledgementmessages. The operations of 1520 may be performed according to themethods described herein. In some examples, aspects of the operations of1520 may be performed by an acknowledgement codebook generator asdescribed with reference to FIGS. 5 through 8.

At 1525, the UE may determine that downlink control informationscheduling downlink data transmissions is received before the downlinkcontrol transmission that schedules the uplink transmissions for theslot. The operations of 1525 may be performed according to the methodsdescribed herein. In some examples, aspects of the operations of 1525may be performed by an acknowledgement codebook multiplexer as describedwith reference to FIGS. 5 through 8.

At 1530, the UE may multiplex, based on the set of timing thresholdsbeing satisfied, the one or more acknowledgement codebooks with theuplink data transmission on an uplink data channel based on the downlinkcontrol information being received before the downlink controltransmission. The operations of 1530 may be performed according to themethods described herein. In some examples, aspects of the operations of1530 may be performed by an acknowledgement codebook multiplexer asdescribed with reference to FIGS. 5 through 8.

FIG. 16 shows a flowchart illustrating a method 1600 that supportshandling collisions between multiple acknowledgement transmissions andan uplink data transmission in accordance with aspects of the presentdisclosure. The operations of method 1600 may be implemented by a UE 115or its components as described herein. For example, the operations ofmethod 1600 may be performed by a communications manager as describedwith reference to FIGS. 5 through 8. In some examples, a UE may executea set of instructions to control the functional elements of the UE toperform the functions described below. Additionally or alternatively, aUE may perform aspects of the functions described below usingspecial-purpose hardware.

At 1605, the UE may identify that an uplink data transmission scheduledin a slot overlaps with multiple scheduled transmission acknowledgementmessages. The operations of 1605 may be performed according to themethods described herein. In some examples, aspects of the operations of1605 may be performed by an uplink data transmission identifier asdescribed with reference to FIGS. 5 through 8.

At 1610, the UE may determine that a set of timing thresholds aresatisfied by an earliest of the multiple scheduled transmissionacknowledgement messages and the uplink data transmission with respectto a latest downlink data transmission acknowledged by one of themultiple scheduled transmission acknowledgement messages and a downlinkcontrol transmission that schedules the uplink data transmission. Theoperations of 1610 may be performed according to the methods describedherein. In some examples, aspects of the operations of 1610 may beperformed by a timing threshold satisfaction determiner as describedwith reference to FIGS. 5 through 8.

At 1615, the UE may generate one or more acknowledgement codebooks fortransmission of the multiple scheduled transmission acknowledgementmessages. The operations of 1615 may be performed according to themethods described herein. In some examples, aspects of the operations of1615 may be performed by an acknowledgement codebook generator asdescribed with reference to FIGS. 5 through 8.

At 1620, the UE may determine that downlink control informationscheduling one or more downlink data transmissions is received after thedownlink control transmission that schedules the uplink datatransmission. The operations of 1620 may be performed according to themethods described herein. In some examples, aspects of the operations of1620 may be performed by an acknowledgement codebook multiplexer asdescribed with reference to FIGS. 5 through 8.

At 1625, the UE may multiplex, based on the set of timing thresholdsbeing satisfied, the one or more acknowledgement codebooks with theuplink data transmission on an uplink data channel, whereacknowledgement codebooks corresponding to responsive transmissionacknowledgement messages associated with the one or more of the downlinkdata transmissions received after the downlink control transmission arenot included in generating the one or more acknowledgement codebooks.The operations of 1625 may be performed according to the methodsdescribed herein. In some examples, aspects of the operations of 1625may be performed by an acknowledgement codebook multiplexer as describedwith reference to FIGS. 5 through 8.

FIG. 17 shows a flowchart illustrating a method 1700 that supportshandling collisions between multiple acknowledgement transmissions andan uplink data transmission in accordance with aspects of the presentdisclosure. The operations of method 1700 may be implemented by a UE 115or its components as described herein. For example, the operations ofmethod 1700 may be performed by a communications manager as describedwith reference to FIGS. 5 through 8. In some examples, a UE may executea set of instructions to control the functional elements of the UE toperform the functions described below. Additionally or alternatively, aUE may perform aspects of the functions described below usingspecial-purpose hardware.

At 1705, the UE may identify that an uplink data transmission scheduledin a slot overlaps with multiple scheduled transmission acknowledgementmessages. The operations of 1705 may be performed according to themethods described herein. In some examples, aspects of the operations of1705 may be performed by an uplink data transmission identifier asdescribed with reference to FIGS. 5 through 8.

At 1710, the UE may determine that a set of timing thresholds aresatisfied by an earliest of the multiple scheduled transmissionacknowledgement messages and the uplink data transmission with respectto a latest downlink data transmission acknowledged by one of themultiple scheduled transmission acknowledgement messages and a downlinkcontrol transmission that schedules the uplink data transmission. Theoperations of 1710 may be performed according to the methods describedherein. In some examples, aspects of the operations of 1710 may beperformed by a timing threshold satisfaction determiner as describedwith reference to FIGS. 5 through 8.

At 1715, the UE may separately encode each of the multiple scheduledtransmission acknowledgement messages to corresponding codedacknowledgment codebooks, where the corresponding acknowledgementcodebooks are each mapped to an uplink data channel. The operations of1715 may be performed according to the methods described herein. In someexamples, aspects of the operations of 1715 may be performed by atransmission acknowledgement message encoder as described with referenceto FIGS. 5 through 8.

At 1720, the UE may multiplex, based on the set of timing thresholdsbeing satisfied, the corresponding acknowledgement codebooks with theuplink data transmission on the uplink data channel. The operations of1720 may be performed according to the methods described herein. In someexamples, aspects of the operations of 1720 may be performed by anacknowledgement codebook multiplexer as described with reference toFIGS. 5 through 8.

FIG. 18 shows a flowchart illustrating a method 1800 that supportshandling collisions between multiple acknowledgement transmissions andan uplink data transmission in accordance with aspects of the presentdisclosure. The operations of method 1800 may be implemented by a UE 115or its components as described herein. For example, the operations ofmethod 1800 may be performed by a communications manager as describedwith reference to FIGS. 5 through 8. In some examples, a UE may executea set of instructions to control the functional elements of the UE toperform the functions described below. Additionally or alternatively, aUE may perform aspects of the functions described below usingspecial-purpose hardware.

At 1805, the UE may identify that an uplink data transmission in a slotoverlaps with multiple scheduled transmission acknowledgement messages.The operations of 1805 may be performed according to the methodsdescribed herein. In some examples, aspects of the operations of 1805may be performed by an uplink data transmission identifier as describedwith reference to FIGS. 5 through 8.

At 1810, the UE may determine that a set of timing thresholds aresatisfied by an earliest of the multiple scheduled transmissionacknowledgement messages and the uplink data transmission with respectto a latest downlink data transmission acknowledged by one of themultiple scheduled transmission acknowledgement messages and a downlinkcontrol transmission that schedules the uplink data transmission. Theoperations of 1810 may be performed according to the methods describedherein. In some examples, aspects of the operations of 1810 may beperformed by a timing threshold satisfaction determiner as describedwith reference to FIGS. 5 through 8.

At 1815, the UE may jointly encode the multiple scheduled transmissionacknowledgement messages to a single coded acknowledgement codebook,where the single coded acknowledgement codebook is mapped to an uplinkdata channel. The operations of 1815 may be performed according to themethods described herein. In some examples, aspects of the operations of1815 may be performed by a transmission acknowledgement message encoderas described with reference to FIGS. 5 through 8.

At 1820, the UE may multiplex, based on the set of timing thresholdsbeing satisfied, the single coded acknowledgement codebook with theuplink data transmission on the uplink data channel. The operations of1820 may be performed according to the methods described herein. In someexamples, aspects of the operations of 1820 may be performed by anacknowledgement codebook multiplexer as described with reference toFIGS. 5 through 8.

FIG. 19 shows a flowchart illustrating a method 1900 that supportshandling collisions between multiple acknowledgement transmissions andan uplink data transmission in accordance with aspects of the presentdisclosure. The operations of method 1900 may be implemented by a UE 115or its components as described herein. For example, the operations ofmethod 1900 may be performed by a communications manager as describedwith reference to FIGS. 5 through 8. In some examples, a UE may executea set of instructions to control the functional elements of the UE toperform the functions described below. Additionally or alternatively, aUE may perform aspects of the functions described below usingspecial-purpose hardware.

At 1905, the UE may identify that an uplink data transmission scheduledin a slot overlaps with multiple scheduled transmission acknowledgementmessages. The operations of 1905 may be performed according to themethods described herein. In some examples, aspects of the operations of1905 may be performed by an uplink data transmission identifier asdescribed with reference to FIGS. 5 through 8.

At 1910, the UE may receive a single second indication ofacknowledgement payload size via a downlink control transmission thatschedules the uplink data transmission. The operations of 1910 may beperformed according to the methods described herein. In some examples,aspects of the operations of 1910 may be performed by an acknowledgementpayload size indicator as described with reference to FIGS. 5 through 8.

At 1915, the UE may determine that a set of timing thresholds aresatisfied by an earliest of the multiple transmission acknowledgementmessages and the uplink data transmission with respect to a latestdownlink data transmission acknowledged by one of the multipletransmission acknowledgement messages and the downlink controltransmission that schedules the uplink data transmission. The operationsof 1915 may be performed according to the methods described herein. Insome examples, aspects of the operations of 1915 may be performed by atiming threshold satisfaction determiner as described with reference toFIGS. 5 through 8.

At 1920, the UE may receive a set of first indications ofacknowledgement payload size, each of the set of first indicationscorresponding to one of the multiple scheduled transmissionacknowledgement messages and being received via respective downlinkcontrol information messages scheduling downlink data transmissionsacknowledged by the multiple transmission acknowledgement messages. Theoperations of 1920 may be performed according to the methods describedherein. In some examples, aspects of the operations of 1920 may beperformed by an acknowledgement payload size indicator as described withreference to FIGS. 5 through 8.

At 1925, the UE may generate one or more acknowledgement codebooks fortransmission of the multiple scheduled transmission acknowledgementmessages. The operations of 1925 may be performed according to themethods described herein. In some examples, aspects of the operations of1925 may be performed by an acknowledgement codebook generator asdescribed with reference to FIGS. 5 through 8.

At 1930, the UE may multiplex, based on the set of timing thresholdsbeing satisfied, the one or more acknowledgement codebooks with theuplink data transmission on an uplink data channel. The operations of1930 may be performed according to the methods described herein. In someexamples, aspects of the operations of 1930 may be performed by anacknowledgement codebook multiplexer as described with reference toFIGS. 5 through 8.

FIG. 20 shows a flowchart illustrating a method 2000 that supportshandling collisions between multiple acknowledgement transmissions andan uplink data transmission in accordance with aspects of the presentdisclosure. The operations of method 2000 may be implemented by a basestation 105 or its components as described herein. For example, theoperations of method 2000 may be performed by a communications manageras described with reference to FIGS. 9 through 12. In some examples, abase station may execute a set of instructions to control the functionalelements of the base station to perform the functions described below.Additionally or alternatively, a base station may perform aspects of thefunctions described below using special-purpose hardware.

At 2005, the base station may transmit, to a UE, a downlink controltransmission scheduling an uplink data transmission by the UE during aslot. The operations of 2005 may be performed according to the methodsdescribed herein. In some examples, aspects of the operations of 2005may be performed by a downlink control transmission transmitter asdescribed with reference to FIGS. 9 through 12.

At 2010, the base station may transmit, to the UE, multiple downlinkdata transmissions that are to be acknowledged by the UE viacorresponding multiple transmission acknowledgment messages that arescheduled to at least partially overlap in time with the uplink datatransmission. The operations of 2010 may be performed according to themethods described herein. In some examples, aspects of the operations of2010 may be performed by a downlink data transmission transmitter asdescribed with reference to FIGS. 9 through 12.

At 2015, the base station may receive, from the UE, one or moreacknowledgement codebooks corresponding to the multiple transmissionacknowledgement messages, where the one or more acknowledgementcodebooks are multiplexed with the uplink data transmission based on aset of timing thresholds being satisfied by an earliest of the multipletransmission acknowledgement messages and the uplink data transmissionwith respect to a latest downlink data transmission of the multipledownlink data transmissions and the downlink control transmissionscheduling the uplink data transmission. The operations of 2015 may beperformed according to the methods described herein. In some examples,aspects of the operations of 2015 may be performed by an acknowledgementcodebook receiver as described with reference to FIGS. 9 through 12.

It should be noted that the methods described herein describe possibleimplementations, and that the operations and the steps may be rearrangedor otherwise modified and that other implementations are possible.Further, aspects from two or more of the methods may be combined.

Techniques described herein may be used for various wirelesscommunications systems such as code division multiple access (CDMA),time division multiple access (TDMA), frequency division multiple access(FDMA), orthogonal frequency division multiple access (OFDMA), singlecarrier frequency division multiple access (SC-FDMA), and other systems.A CDMA system may implement a radio technology such as CDMA2000,Universal Terrestrial Radio Access (UTRA), etc. CDMA2000 covers IS-2000,IS-95, and IS-856 standards. IS-2000 Releases may be commonly referredto as CDMA2000 1×, 1×, etc. IS-856 (TIA-856) is commonly referred to asCDMA2000 1×EV-DO, High Rate Packet Data (HRPD), etc. UTRA includesWideband CDMA (WCDMA) and other variants of CDMA. A TDMA system mayimplement a radio technology such as Global System for MobileCommunications (GSM).

An OFDMA system may implement a radio technology such as Ultra MobileBroadband (UMB), Evolved UTRA (E-UTRA), Institute of Electrical andElectronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE802.20, Flash-OFDM, etc. UTRA and E-UTRA are part of Universal MobileTelecommunications System (UMTS). LTE, LTE-A, and LTE-A Pro are releasesof UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, LTE-A Pro, NR,and GSM are described in documents from the organization named “3rdGeneration Partnership Project” (3GPP). CDMA2000 and UMB are describedin documents from an organization named “3rd Generation PartnershipProject 2” (3GPP2). The techniques described herein may be used for thesystems and radio technologies mentioned herein as well as other systemsand radio technologies. While aspects of an LTE, LTE-A, LTE-A Pro, or NRsystem may be described for purposes of example, and LTE, LTE-A, LTE-APro, or NR terminology may be used in much of the description, thetechniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro,or NR applications.

A macro cell generally covers a relatively large geographic area (e.g.,several kilometers in radius) and may allow unrestricted access by UEswith service subscriptions with the network provider. A small cell maybe associated with a lower-powered base station, as compared with amacro cell, and a small cell may operate in the same or different (e.g.,licensed, unlicensed, etc.) frequency bands as macro cells. Small cellsmay include pico cells, femto cells, and micro cells according tovarious examples. A pico cell, for example, may cover a small geographicarea and may allow unrestricted access by UEs with service subscriptionswith the network provider. A femto cell may also cover a smallgeographic area (e.g., a home) and may provide restricted access by UEshaving an association with the femto cell (e.g., UEs in a closedsubscriber group (CSG), UEs for users in the home, and the like). An eNBfor a macro cell may be referred to as a macro eNB. An eNB for a smallcell may be referred to as a small cell eNB, a pico eNB, a femto eNB, ora home eNB. An eNB may support one or multiple (e.g., two, three, four,and the like) cells, and may also support communications using one ormultiple component carriers.

The wireless communications systems described herein may supportsynchronous or asynchronous operation. For synchronous operation, thebase stations may have similar frame timing, and transmissions fromdifferent base stations may be approximately aligned in time. Forasynchronous operation, the base stations may have different frametiming, and transmissions from different base stations may not bealigned in time. The techniques described herein may be used for eithersynchronous or asynchronous operations.

Information and signals described herein may be represented using any ofa variety of different technologies and techniques. For example, data,instructions, commands, information, signals, bits, symbols, and chipsthat may be referenced throughout the description may be represented byvoltages, currents, electromagnetic waves, magnetic fields or particles,optical fields or particles, or any combination thereof.

Aspects of the following examples may be combined with any of theprevious examples or aspects described herein.

Example 1

A method for wireless communication at a UE, comprising: identifyingthat an uplink data transmission scheduled in a slot overlaps withmultiple scheduled transmission acknowledgement messages; determiningthat a plurality of timing thresholds are satisfied by an earliest ofthe multiple scheduled transmission acknowledgement messages and theuplink data transmission with respect to a latest downlink datatransmission acknowledged by one of the multiple scheduled transmissionacknowledgement messages and a downlink control transmission thatschedules the uplink data transmission; generating one or moreacknowledgement codebooks for transmission of the multiple scheduledtransmission acknowledgement messages; and multiplexing, based at leastin part on the plurality of timing thresholds being satisfied, the oneor more acknowledgement codebooks with the uplink data transmission onan uplink data channel.

Example 2

The method of example 1, wherein determining that the plurality oftiming thresholds are satisfied comprises: determining that a firsttiming threshold is satisfied by the earliest of the multiple scheduledtransmission acknowledgement messages and the uplink data transmissionbeing at least a first predetermined number of symbols after a lastsymbol of the latest downlink data transmission acknowledged by one ofthe multiple transmission acknowledgment messages; and determining thata second timing threshold is satisfied by the earliest of the multiplescheduled transmission acknowledgement messages and the uplink datatransmission being at least a second predetermined number of symbolsafter a last symbol of the downlink control transmission that schedulesthe uplink data transmission.

Example 3

The method of any of examples 1 or 2, further comprising: determiningthat downlink control information scheduling downlink data transmissionsis received before the downlink control transmission that schedules theuplink data transmission, wherein multiplexing the one or moreacknowledgement codebooks with the uplink data transmission is furtherbased on the downlink control information being received before thedownlink control transmission.

Example 4

The method of any of examples 1 to 3, further comprising: determiningthat downlink control information scheduling one or more downlink datatransmissions is received after the downlink control transmission thatschedules the uplink data transmission, wherein acknowledgementcodebooks corresponding to responsive transmission acknowledgementmessages associated with the one or more downlink data transmissionsreceived after the downlink control transmission are not included ingenerating the one or more acknowledgement codebooks.

Example 5

The method of any of examples 1 to 4, wherein generating the one or moreacknowledgement codebooks for transmission of the multiple scheduledtransmission acknowledgement messages comprises: separately encodingeach of the multiple scheduled transmission acknowledgement messages tocorresponding coded acknowledgment codebooks, wherein the correspondingacknowledgement codebooks are each mapped to the uplink data channel.

Example 6

The method of any of examples 1 to 5, wherein generating the one or moreacknowledgement codebooks for transmission of the multiple scheduledtransmission acknowledgement messages comprises: jointly encoding themultiple scheduled transmission acknowledgement messages to a singlecoded acknowledgement codebook, wherein the single coded acknowledgementcodebook is mapped to the uplink data channel.

Example 7

The method of any of examples 1 to 6, further comprising: receiving aplurality of first indications of acknowledgement payload size, each ofthe plurality of first indications corresponding to one of the multiplescheduled transmission acknowledgement messages and being received viarespective downlink control information messages scheduling downlinkdata transmissions acknowledged by the multiple scheduled transmissionacknowledgement messages; and receiving a single second indication ofacknowledgement payload size via the downlink control transmission thatschedules the uplink data transmission.

Example 8

The method of any of examples 1 to 7, wherein generating the one or moreacknowledgement codebooks for transmission of the multiple scheduledtransmission acknowledgement messages comprises: generating a separateacknowledgement codebook for each of the multiple scheduled transmissionacknowledgement messages based on respective ones of the plurality offirst indications; and padding one or more of the separateacknowledgement codebooks according to the single second indication togenerate a plurality of updated acknowledgement codebooks formultiplexing the one or more acknowledgement codebooks with the uplinkdata transmission.

Example 9

The method of any of examples 1 to 8, further comprising: concatenatingeach of the plurality of updated acknowledgement codebooks prior tomultiplexing the one or more acknowledgement codebooks with the uplinkdata transmission.

Example 10

The method of any of examples 1 to 9, wherein generating the one or moreacknowledgement codebooks for transmission of the multiple scheduledtransmission acknowledgement messages comprises: generating a separateacknowledgement codebook for each of the multiple scheduled transmissionacknowledgement messages based on respective ones of the plurality offirst indications; concatenating the separate acknowledgement codebooksfor each of the multiple scheduled transmission acknowledgementmessages; and applying the single second indication to the concatenatedacknowledgement codebooks to generate a single updated acknowledgementcodebook for multiplexing the one or more acknowledgement codebooks withthe uplink data transmission.

Example 11

The method of any of examples 1 to 10, wherein the multiple scheduledtransmission acknowledgement messages are each scheduled to betransmitted via separate physical uplink control channel transmissionswithin the slot.

Example 12

The method of any of examples 1 to 11, wherein the multiple scheduledtransmission acknowledgement messages are scheduled to be transmitted ona first carrier that has a higher sub-carrier spacing than that of asecond carrier used by the uplink data transmission, and wherein themultiple scheduled transmission acknowledgement messages are eachscheduled to be transmitted via separate physical uplink control channeltransmissions within corresponding slots of the first carrier.

Example 13

The method of any of examples 1 to 12, wherein the multiple scheduledtransmission acknowledgement messages and the uplink data transmissionare each associated with a same traffic type.

Example 14

The method of any of examples 1 to 13, wherein the same traffic type isultra-reliable low-latency communications traffic.

Example 15

The method of any of examples 1 to 14, wherein the same traffic type isenhanced mobile broadband traffic.

Example 16

An apparatus comprising at least one means for performing a method ofany of examples 1 to 15.

Example 17

An apparatus for wireless communications comprising a processor; memorycoupled with the processor; and instructions stored in the memory andexecutable by the processor to cause the apparatus to perform a methodof any of examples 1 to 15.

Example 18

A non-transitory computer-readable medium storing code for wirelesscommunications, the code comprising instructions executable by aprocessor to perform a method of any of examples 1 to 15.

Example 19

A method for wireless communication at a base station, comprising:transmitting, to a user equipment (UE), a downlink control transmissionscheduling an uplink data transmission for the UE during a slot;transmitting, to the UE, multiple downlink data transmissions that areto be acknowledged by the UE via corresponding multiple transmissionacknowledgment messages that are scheduled to at least partially overlapin time with the uplink data transmission; and receiving, from the UE,one or more acknowledgement codebooks corresponding to the multipletransmission acknowledgement messages, wherein the one or moreacknowledgement codebooks are multiplexed with the uplink datatransmission based at least in part on a plurality of timing thresholdsbeing satisfied by an earliest of the multiple transmissionacknowledgement messages and the uplink data transmission with respectto a latest downlink data transmission of the multiple downlink datatransmissions and the downlink control transmission scheduling theuplink data transmission.

Example 20

The method of example 19, wherein the plurality of timing thresholdscomprise a first timing threshold and a second timing threshold, thefirst timing threshold being satisfied by the earliest of the multipletransmission acknowledgement messages and the uplink data transmissionbeing at least a first predetermined number of symbols after a lastsymbol of the latest downlink data transmission of the multiple downlinkdata transmissions, and the second timing threshold being satisfied bythe earliest of the multiple transmission acknowledgement messages andthe uplink data transmission being at least a second predeterminednumber of symbols after a last symbol of the downlink controltransmission scheduling the uplink data transmission.

Example 21

The method of any of examples 19 or 20, wherein receiving one or moreacknowledgement codebooks corresponding to the multiple transmissionacknowledgement messages and multiplexed with the uplink datatransmission is further based on downlink control information schedulingthe multiple downlink data transmissions being received at the UE beforethe downlink control transmission scheduling the uplink datatransmission.

Example 22

The method of any of examples 19 to 21, further comprising: transmittinga downlink control information scheduling at least one of the multipledownlink data transmissions such that the downlink control informationis received at the UE after the downlink control transmission schedulingthe uplink data transmission, wherein ones of the multiple transmissionacknowledgement messages that are responsive to the at least one of themultiple downlink data transmissions are not included in the one or moreacknowledgement codebooks multiplexed with the uplink data transmissionreceived from the UE.

Example 23

The method of any of examples 19 to 22, wherein receiving one or moreacknowledgement codebooks corresponding to the multiple transmissionacknowledgement messages and multiplexed with the uplink datatransmission comprises: receiving the multiple transmissionacknowledgement messages as separately encoded acknowledgementcodebooks.

Example 24

The method of any of examples 19 to 23, wherein receiving one or moreacknowledgement codebooks corresponding to the multiple transmissionacknowledgement messages and multiplexed with the uplink datatransmission comprises: receiving the multiple transmissionacknowledgement messages as a jointly encoded acknowledgement codebook.

Example 25

The method of any of examples 19 to 24, further comprising: transmittinga plurality of first indications of acknowledgement payload size, eachof the plurality of first indications corresponding to one of themultiple transmission acknowledgement messages and being transmitted viarespective downlink control information messages scheduling the multipledownlink data transmissions; and transmitting a single second indicationof acknowledgement payload size via the downlink control transmissionscheduling the uplink data transmission.

Example 26

The method of any of examples 19 to 25, wherein the single secondindication is indicative of acknowledgement payload size for each of theone or more acknowledgement codebooks, and wherein each of the one ormore acknowledgement codebooks is a coded acknowledgement codebook.

Example 27

The method of any of examples 19 to 26, wherein the single secondindication is indicative of a single coded acknowledgement payload sizefor all of the one or more acknowledgement codebooks.

Example 28

The method of any of examples 19 to 27, wherein the multipletransmission acknowledgement messages are each scheduled to betransmitted via separate physical uplink control channel transmissionswithin the slot.

Example 29

The method of any of examples 19 to 28, wherein the multipletransmission acknowledgement messages are scheduled to be transmitted ona first carrier that has a higher sub-carrier spacing than that of asecond carrier used by the uplink data transmission, and wherein themultiple transmission acknowledgement messages are each scheduled to betransmitted via separate physical uplink control channel transmissionswithin corresponding slots of the first carrier.

Example 30

The method of any of examples 19 to 29, wherein the multipletransmission acknowledgement messages and the uplink data transmissionare each associated with a same traffic type.

Example 31

The method of any of examples 19 to 30, wherein the same traffic type isultra-reliable low-latency communications traffic.

Example 32

The method of any of examples 19 to 31, wherein the same traffic type isenhanced mobile broadband traffic.

Example 33

An apparatus comprising at least one means for performing a method ofany of examples 19 to 32.

Example 34

An apparatus for wireless communications comprising a processor; memorycoupled with the processor; and instructions stored in the memory andexecutable by the processor to cause the apparatus to perform a methodof any of examples 19 to 32.

Example 35

A non-transitory computer-readable medium storing code for wirelesscommunications, the code comprising instructions executable by aprocessor to perform a method of any of examples 19 to 32.

The various illustrative blocks and modules described in connection withthe disclosure herein may be implemented or performed with ageneral-purpose processor, a DSP, an ASIC, an FPGA, or otherprogrammable logic device, discrete gate or transistor logic, discretehardware components, or any combination thereof designed to perform thefunctions described herein. A general-purpose processor may be amicroprocessor, but in the alternative, the processor may be anyconventional processor, controller, microcontroller, or state machine. Aprocessor may also be implemented as a combination of computing devices(e.g., a combination of a DSP and a microprocessor, multiplemicroprocessors, one or more microprocessors in conjunction with a DSPcore, or any other such configuration).

The functions described herein may be implemented in hardware, softwareexecuted by a processor, firmware, or any combination thereof. Ifimplemented in software executed by a processor, the functions may bestored on or transmitted over as one or more instructions or code on acomputer-readable medium. Other examples and implementations are withinthe scope of the disclosure and appended claims. For example, due to thenature of software, functions described herein can be implemented usingsoftware executed by a processor, hardware, firmware, hardwiring, orcombinations of any of these. Features implementing functions may alsobe physically located at various positions, including being distributedsuch that portions of functions are implemented at different physicallocations.

Computer-readable media includes both non-transitory computer storagemedia and communication media including any medium that facilitatestransfer of a computer program from one place to another. Anon-transitory storage medium may be any available medium that can beaccessed by a general purpose or special-purpose computer. By way ofexample, and not limitation, non-transitory computer-readable media mayinclude RAM, ROM, electrically erasable programmable ROM (EEPROM), flashmemory, compact disk (CD) ROM or other optical disk storage, magneticdisk storage or other magnetic storage devices, or any othernon-transitory medium that can be used to carry or store desired programcode means in the form of instructions or data structures and that canbe accessed by a general-purpose or special-purpose computer, or ageneral-purpose or special-purpose processor. Also, any connection isproperly termed a computer-readable medium. For example, if the softwareis transmitted from a website, server, or other remote source using acoaxial cable, fiber optic cable, twisted pair, digital subscriber line(DSL), or wireless technologies such as infrared, radio, and microwave,then the coaxial cable, fiber optic cable, twisted pair, DSL, orwireless technologies such as infrared, radio, and microwave areincluded in the definition of medium. Disk and disc, as used herein,include CD, laser disc, optical disc, digital versatile disc (DVD),floppy disk and Blu-ray disc where disks usually reproduce datamagnetically, while discs reproduce data optically with lasers.Combinations of the above are also included within the scope ofcomputer-readable media.

As used herein, including in the claims, “or” as used in a list of items(e.g., a list of items prefaced by a phrase such as “at least one of” or“one or more of”) indicates an inclusive list such that, for example, alist of at least one of A, B, or C means A or B or C or AB or AC or BCor ABC (i.e., A and B and C). Also, as used herein, the phrase “basedon” shall not be construed as a reference to a closed set of conditions.For example, an exemplary step that is described as “based on conditionA” may be based on both a condition A and a condition B withoutdeparting from the scope of the present disclosure. In other words, asused herein, the phrase “based on” shall be construed in the same manneras the phrase “based at least in part on.”

In the appended figures, similar components or features may have thesame reference label. Further, various components of the same type maybe distinguished by following the reference label by a dash and a secondlabel that distinguishes among the similar components. If just the firstreference label is used in the specification, the description isapplicable to any one of the similar components having the same firstreference label irrespective of the second reference label, or othersubsequent reference label.

The description set forth herein, in connection with the appendeddrawings, describes example configurations and does not represent allthe examples that may be implemented or that are within the scope of theclaims. The term “exemplary” used herein means “serving as an example,instance, or illustration,” and not “preferred” or “advantageous overother examples.” The detailed description includes specific details forthe purpose of providing an understanding of the described techniques.These techniques, however, may be practiced without these specificdetails. In some instances, well-known structures and devices are shownin block diagram form in order to avoid obscuring the concepts of thedescribed examples.

The description herein is provided to enable a person skilled in the artto make or use the disclosure. Various modifications to the disclosurewill be readily apparent to those skilled in the art, and the genericprinciples defined herein may be applied to other variations withoutdeparting from the scope of the disclosure. Thus, the disclosure is notlimited to the examples and designs described herein, but is to beaccorded the broadest scope consistent with the principles and novelfeatures disclosed herein.

What is claimed is:
 1. A method for wireless communication at a userequipment (UE), comprising: identifying that an uplink shared channeltransmission scheduled in a slot overlaps with multiple scheduledtransmission acknowledgement messages; determining that a plurality oftiming thresholds are satisfied by an earliest of the multiple scheduledtransmission acknowledgement messages and the uplink shared channeltransmission with respect to a latest downlink data transmissionacknowledged by one of the multiple scheduled transmissionacknowledgement messages and a downlink control transmission thatschedules the uplink shared channel transmission; generating a pluralityof acknowledgement codebooks for transmission of the multiple scheduledtransmission acknowledgement messages; and multiplexing, based at leastin part on the plurality of timing thresholds being satisfied anddownlink control information scheduling the latest downlink datatransmission being received before the downlink control transmissionscheduling the uplink shared channel transmission, the plurality ofacknowledgement codebooks with the uplink shared channel transmission onan uplink data channel.
 2. The method of claim 1, wherein determiningthat the plurality of timing thresholds are satisfied comprises:determining that a first timing threshold is satisfied by the earliestof the multiple scheduled transmission acknowledgement messages and theuplink shared channel transmission being at least a first predeterminednumber of symbols after a last symbol of the latest downlink datatransmission acknowledged by one of the multiple scheduled transmissionacknowledgment messages; and determining that a second timing thresholdis satisfied by the earliest of the multiple scheduled transmissionacknowledgement messages and the uplink shared channel transmissionbeing at least a second predetermined number of symbols after a lastsymbol of the downlink control transmission that schedules the uplinkshared channel transmission.
 3. The method of claim 1, furthercomprising: determining that the downlink control information schedulingthe latest downlink data transmission is received after the downlinkcontrol transmission that schedules the uplink shared channeltransmission, wherein acknowledgement codebooks corresponding torespective transmission acknowledgement messages associated with thelatest downlink data transmission received after the downlink controltransmission are not included in generating the plurality ofacknowledgement codebooks.
 4. The method of claim 1, wherein generatingthe plurality of acknowledgement codebooks for transmission of themultiple scheduled transmission acknowledgement messages comprises:separately encoding each of the multiple scheduled transmissionacknowledgement messages in the slot in which the uplink shared channeltransmission is scheduled to corresponding coded acknowledgmentcodebooks, wherein the corresponding acknowledgement codebooks are eachmapped to the uplink data channel.
 5. The method of claim 1, furthercomprising: receiving a plurality of first indications ofacknowledgement payload size, each of the plurality of first indicationscorresponding to one of the multiple scheduled transmissionacknowledgement messages and being received via respective downlinkcontrol information messages scheduling downlink data transmissionsacknowledged by the multiple scheduled transmission acknowledgementmessages; and receiving a single second indication of acknowledgementpayload size via the downlink control transmission that schedules theuplink shared channel transmission.
 6. The method of claim 5, whereingenerating the plurality of acknowledgement codebooks for transmissionof the multiple scheduled transmission acknowledgement messagescomprises: generating a separate acknowledgement codebook for each ofthe multiple scheduled transmission acknowledgement messages based onrespective ones of the plurality of first indications; and padding atleast one or more of the separate acknowledgement codebooks according tothe single second indication to generate a plurality of updatedacknowledgement codebooks for multiplexing the plurality ofacknowledgement codebooks with the uplink shared channel transmission.7. The method of claim 6, further comprising: concatenating each of theplurality of updated acknowledgement codebooks prior to multiplexing theplurality of acknowledgement codebooks with the uplink shared channeltransmission.
 8. The method of claim 5, wherein generating the pluralityof acknowledgement codebooks for transmission of the multiple scheduledtransmission acknowledgement messages comprises: generating a separateacknowledgement codebook for each of the multiple scheduled transmissionacknowledgement messages based on respective ones of the plurality offirst indications; concatenating the separate acknowledgement codebooksfor each of the multiple scheduled transmission acknowledgementmessages; and applying the single second indication to the concatenatedacknowledgement codebooks to generate a single updated acknowledgementcodebook for multiplexing the plurality of acknowledgement codebookswith the uplink shared channel transmission.
 9. The method of claim 1,wherein the multiple scheduled transmission acknowledgement messages areeach scheduled to be transmitted via separate physical uplink controlchannel transmissions within the slot.
 10. The method of claim 1,wherein the multiple scheduled transmission acknowledgement messages arescheduled to be transmitted on a first carrier that has a highersub-carrier spacing than that of a second carrier used by the uplinkshared channel transmission, and wherein the multiple scheduledtransmission acknowledgement messages are each scheduled to betransmitted via separate physical uplink control channel transmissionswithin corresponding slots of the first carrier.
 11. The method of claim1, wherein the multiple scheduled transmission acknowledgement messagesand the uplink shared channel transmission are each associated with asame traffic type.
 12. A method for wireless communication at a basestation, comprising: transmitting, to a user equipment (UE), a downlinkcontrol transmission scheduling an uplink shared channel transmissionfor the UE during a slot; transmitting, to the UE, multiple downlinkdata transmissions that are to be acknowledged by the UE viacorresponding multiple transmission acknowledgment messages that arescheduled to at least partially overlap in time with the uplink sharedchannel transmission; and receiving, from the UE, a plurality ofacknowledgement codebooks corresponding to the multiple transmissionacknowledgement messages, wherein the plurality of acknowledgementcodebooks are multiplexed with the uplink shared channel transmissionbased at least in part on a plurality of timing thresholds beingsatisfied by an earliest of the multiple transmission acknowledgementmessages and the uplink shared channel transmission with respect to alatest downlink data transmission of the multiple downlink datatransmissions and the downlink control transmission scheduling theuplink shared channel transmission and based at least in part ondownlink control information scheduling the latest downlink datatransmission being received at the UE before the downlink controltransmission scheduling the uplink shared channel transmission.
 13. Themethod of claim 12, wherein the plurality of timing thresholds comprisea first timing threshold and a second timing threshold, the first timingthreshold being satisfied by the earliest of the multiple transmissionacknowledgement messages and the uplink shared channel transmissionbeing at least a first predetermined number of symbols after a lastsymbol of the latest downlink data transmission of the multiple downlinkdata transmissions, and the second timing threshold being satisfied bythe earliest of the multiple transmission acknowledgement messages andthe uplink shared channel transmission being at least a secondpredetermined number of symbols after a last symbol of the downlinkcontrol transmission scheduling the uplink shared channel transmission.14. The method of claim 12, further comprising: transmitting thedownlink control information scheduling the latest downlink datatransmission such that the downlink control information is received atthe UE after the downlink control transmission scheduling the uplinkshared channel transmission, wherein one or more of the multipletransmission acknowledgement messages that correspond to at least one ofthe multiple downlink data transmissions are not included in theplurality of acknowledgement codebooks multiplexed with the uplinkshared channel transmission received from the UE.
 15. The method ofclaim 12, wherein receiving plurality of acknowledgement codebookscorresponding to the multiple transmission acknowledgement messages andmultiplexed with the uplink shared channel transmission comprises:receiving the multiple transmission acknowledgement messages asseparately encoded acknowledgement codebooks.
 16. The method of claim12, further comprising: transmitting a plurality of first indications ofacknowledgement payload size, each of the plurality of first indicationscorresponding to one of the multiple transmission acknowledgementmessages and being transmitted via respective downlink controlinformation messages scheduling the multiple downlink datatransmissions; and transmitting a single second indication ofacknowledgement payload size via the downlink control transmissionscheduling the uplink shared channel transmission.
 17. The method ofclaim 16, wherein the single second indication is indicative ofacknowledgement payload size for each of the plurality ofacknowledgement codebooks, and wherein each of the plurality ofacknowledgement codebooks is a coded acknowledgement codebook.
 18. Themethod of claim 16, wherein the single second indication is indicativeof a single coded acknowledgement payload size for all of the pluralityof acknowledgement codebooks.
 19. The method of claim 12, wherein themultiple transmission acknowledgement messages are each scheduled to betransmitted via separate physical uplink control channel transmissionswithin the slot.
 20. The method of claim 12, wherein the multipletransmission acknowledgement messages are scheduled to be transmitted ona first carrier that has a higher sub-carrier spacing than that of asecond carrier used by the uplink shared channel transmission, andwherein the multiple transmission acknowledgement messages are eachscheduled to be transmitted via separate physical uplink control channeltransmissions within corresponding slots of the first carrier.
 21. Themethod of claim 12, wherein the multiple transmission acknowledgementmessages and the uplink shared channel transmission are each associatedwith a same traffic type.
 22. An apparatus for wireless communication ata user equipment (UE), comprising: a processor, memory coupled with theprocessor; and instructions stored in the memory and executable by theprocessor to cause the apparatus to: identify that an uplink sharedchannel transmission scheduled in a slot overlaps with multiplescheduled transmission acknowledgement messages scheduled at the UE;determine that a plurality of timing thresholds are satisfied by anearliest of the multiple scheduled transmission acknowledgement messagesand the uplink shared channel transmission with respect to a latestdownlink data transmission acknowledged by one of the multiple scheduledtransmission acknowledgement messages and a downlink controltransmission that schedules the uplink shared channel transmission;generate a plurality of acknowledgement codebooks for transmission ofthe multiple scheduled transmission acknowledgement messages; andmultiplex, based at least in part on the plurality of timing thresholdsbeing satisfied and downlink control information scheduling the latestdownlink data transmission being received before the downlink controltransmission scheduling the uplink shared channel transmission, theplurality of acknowledgement codebooks with the uplink shared channeltransmission on an uplink data channel.
 23. The apparatus of claim 22,wherein the instructions to determine that the plurality of timingthresholds are satisfied are executable by the processor to cause theapparatus to: determine that a first timing threshold is satisfied bythe earliest of the multiple scheduled transmission acknowledgementmessages and the uplink shared channel transmission being at least afirst predetermined number of symbols after a last symbol of the latestdownlink data transmission acknowledged by one of the multiple scheduledtransmission acknowledgment messages; and determine that a second timingthreshold is satisfied by the earliest of the multiple scheduledtransmission acknowledgement messages and the uplink shared channeltransmission being at least a second predetermined number of symbolsafter a last symbol of the downlink control transmission that schedulesthe uplink shared channel transmission.
 24. The apparatus of claim 22,wherein the instructions are further executable by the processor tocause the apparatus to: determine that the downlink control informationscheduling the latest downlink data transmission is received after thedownlink control transmission that schedules the uplink shared channeltransmission, wherein acknowledgement codebooks corresponding torespective transmission acknowledgement messages associated with thelatest downlink data transmission received after the downlink controltransmission are not included in generating the plurality ofacknowledgement codebooks.
 25. The apparatus of claim 22, wherein theinstructions to generate the plurality of acknowledgement codebooks fortransmission of the multiple scheduled transmission acknowledgementmessages are executable by the processor to cause the apparatus to:separately encode each of the multiple scheduled transmissionacknowledgement messages in the slot in which the uplink shared channeltransmission is scheduled to corresponding coded acknowledgmentcodebooks, wherein the corresponding acknowledgement codebooks are eachmapped to the uplink data channel.
 26. The apparatus of claim 22,wherein the instructions are further executable by the processor tocause the apparatus to: receive a plurality of first indications ofacknowledgement payload size, each of the plurality of first indicationscorresponding to one of the multiple scheduled transmissionacknowledgement messages and being received via respective downlinkcontrol information messages scheduling downlink data transmissionsacknowledged by the multiple scheduled transmission acknowledgementmessages; and receive a single second indication of acknowledgementpayload size via the downlink control transmission that schedules theuplink shared channel transmission.
 27. The apparatus of claim 26,wherein the instructions to generate the plurality of acknowledgementcodebooks for transmission of the multiple scheduled transmissionacknowledgement messages are executable by the processor to cause theapparatus to: generate a separate acknowledgement codebook for each ofthe multiple scheduled transmission acknowledgement messages based onrespective ones of the plurality of first indications; and pad at leastone or more of the separate acknowledgement codebooks according to thesingle second indication to generate a plurality of updatedacknowledgement codebooks for multiplexing the plurality ofacknowledgement codebooks with the uplink shared channel transmission.28. An apparatus for wireless communication at a base station,comprising: a processor, memory coupled with the processor; andinstructions stored in the memory and executable by the processor tocause the apparatus to: transmit, to a user equipment (UE), a downlinkcontrol transmission scheduling an uplink shared channel transmissionfor the UE during a slot; transmit, to the UE, multiple downlink datatransmissions that are to be acknowledged by the UE via correspondingmultiple transmission acknowledgment messages that are scheduled to atleast partially overlap in time with the uplink shared channeltransmission; and receive, from the UE, a plurality of acknowledgementcodebooks corresponding to the multiple transmission acknowledgementmessages, wherein the plurality of acknowledgement codebooks aremultiplexed with the uplink shared channel transmission based at leastin part on a plurality of timing thresholds being satisfied by anearliest of the multiple transmission acknowledgement messages and theuplink shared channel transmission with respect to a latest downlinkdata transmission of the multiple downlink data transmissions and thedownlink control transmission scheduling the uplink shared channeltransmission and based at least in part on downlink control informationscheduling the latest downlink data transmission being received at theUE before the downlink control transmission scheduling the uplink sharedchannel transmission.
 29. The apparatus of claim 28, wherein theplurality of timing thresholds comprise a first timing threshold and asecond timing threshold, the first timing threshold being satisfied bythe earliest of the multiple transmission acknowledgement messages andthe uplink shared channel transmission being at least a firstpredetermined number of symbols after a last symbol of the latestdownlink data transmission of the multiple downlink data transmissions,and the second timing threshold being satisfied by the earliest of themultiple transmission acknowledgement messages and the uplink sharedchannel transmission being at least a second predetermined number ofsymbols after a last symbol of the downlink control transmissionscheduling the uplink shared channel transmission.
 30. The apparatus ofclaim 28, wherein the instructions are further executable by theprocessor to cause the apparatus to: transmit the downlink controlinformation scheduling the latest downlink data transmission such thatthe downlink control information is received at the UE after thedownlink control transmission scheduling the uplink shared channeltransmission, wherein one or more of the multiple transmissionacknowledgement messages that correspond to at least one of the multipledownlink data transmissions are not included in the plurality ofacknowledgement codebooks multiplexed with the uplink shared channeltransmission received from the UE.
 31. The apparatus of claim 28,wherein the instructions to receive plurality of acknowledgementcodebooks corresponding to the multiple transmission acknowledgementmessages and multiplexed with the uplink shared channel transmission areexecutable by the processor to cause the apparatus to: receive themultiple transmission acknowledgement messages as separately encodedacknowledgement codebooks.
 32. The apparatus of claim 28, wherein theinstructions are further executable by the processor to cause theapparatus to: transmit a plurality of first indications ofacknowledgement payload size, each of the plurality of first indicationscorresponding to one of the multiple transmission acknowledgementmessages and being transmitted via respective downlink controlinformation messages scheduling the multiple downlink datatransmissions; and transmit a single second indication ofacknowledgement payload size via the downlink control transmissionscheduling the uplink shared channel transmission.
 33. An apparatus forwireless communication at a user equipment (UE), comprising: means foridentifying that an uplink shared channel transmission scheduled in aslot overlaps with multiple scheduled transmission acknowledgementmessages; means for determining that a plurality of timing thresholdsare satisfied by an earliest of the multiple scheduled transmissionacknowledgement messages and the uplink shared channel transmission withrespect to a latest downlink data transmission acknowledged by one ofthe multiple scheduled transmission acknowledgement messages and adownlink control transmission that schedules the uplink shared channeltransmission; means for generating a plurality of acknowledgementcodebooks for transmission of the multiple scheduled transmissionacknowledgement messages; and means for multiplexing, based at least inpart on the plurality of timing thresholds being satisfied and downlinkcontrol information scheduling the latest downlink data transmissionbeing received before the downlink control transmission scheduling theuplink shared channel transmission, the plurality of acknowledgementcodebooks with the uplink shared channel transmission on an uplink datachannel.
 34. An apparatus for wireless communication at a base station,comprising: means for transmitting, to a user equipment (UE), a downlinkcontrol transmission scheduling an uplink shared channel transmissionfor the UE during a slot; means for transmitting, to the UE, multipledownlink data transmissions that are to be acknowledged by the UE viacorresponding multiple transmission acknowledgment messages that arescheduled to at least partially overlap in time with the uplink sharedchannel transmission; and means for receiving, from the UE, a pluralityof acknowledgement codebooks corresponding to the multiple transmissionacknowledgement messages, wherein the plurality of acknowledgementcodebooks are multiplexed with the uplink shared channel transmissionbased at least in part on a plurality of timing thresholds beingsatisfied by an earliest of the multiple transmission acknowledgementmessages and the uplink shared channel transmission with respect to alatest downlink data transmission of the multiple downlink datatransmissions and the downlink control transmission scheduling theuplink shared channel transmission and based at least in part ondownlink control information scheduling the latest downlink datatransmission being received at the UE before the downlink controltransmission scheduling the uplink shared channel transmission.
 35. Anon-transitory computer-readable medium storing code for wirelesscommunication at a user equipment (UE), the code comprising instructionsexecutable by a processor to: identify that an uplink shared channeltransmission scheduled at the UE in a slot overlaps with multiplescheduled transmission acknowledgement messages scheduled at the UE;determine that a plurality of timing thresholds are satisfied by anearliest of the multiple scheduled transmission acknowledgement messagesand the uplink shared channel transmission with respect to a latestdownlink data transmission acknowledged by one of the multiple scheduledtransmission acknowledgement messages and a downlink controltransmission that schedules the uplink shared channel transmission;generate a plurality of acknowledgement codebooks for transmission ofthe multiple scheduled transmission acknowledgement messages; andmultiplex, based at least in part on the plurality of timing thresholdsbeing satisfied and downlink control information scheduling the latestdownlink data transmission being received before the downlink controltransmission scheduling the uplink shared channel transmission, theplurality of acknowledgement codebooks with the uplink shared channeltransmission on an uplink data channel.
 36. A non-transitorycomputer-readable medium storing code for wireless communication at abase station, the code comprising instructions executable by a processorto: transmit, to a user equipment (UE), a downlink control transmissionscheduling an uplink shared channel transmission for the UE during aslot; transmit, to the UE, multiple downlink data transmissions that areto be acknowledged by the UE via corresponding multiple transmissionacknowledgment messages that are scheduled to at least partially overlapin time with the uplink shared channel transmission; and receive, fromthe UE, a plurality of acknowledgement codebooks corresponding to themultiple transmission acknowledgement messages, wherein the plurality ofacknowledgement codebooks are multiplexed with the uplink shared channeltransmission based at least in part on a plurality of timing thresholdsbeing satisfied by an earliest of the multiple transmissionacknowledgement messages and the uplink shared channel transmission withrespect to a latest downlink data transmission of the multiple downlinkdata transmissions and the downlink control transmission scheduling theuplink shared channel transmission and based at least in part ondownlink control information scheduling the latest downlink datatransmission being received at the UE before the downlink controltransmission scheduling the uplink shared channel transmission.